Currently, when an Exception happens while deploying the Web Application, the test still runs and then fails, reporting that it cannot find its html element. This is suboptimal, as the test should fail when setup the deploy with a descriptive error message, describing that the deployment failed and why.
Note that reporting the exception could possibly be not that easy, as the deploying happens in the OneTimeSetup, where Exceptions seems not to be optimally picked up by Visual Studio (and als ReSharper). See https://github.com/nunit/nunit/issues/2466 . To be tested how the exception would be reported on our Build Server → Update: All Tests in this assembly fail instantly and the error can be found in the build log.