This change adds a fail-fast mechanism to our E2E tests based on the browser console. This will fail super hard if an unhandled exception is thrown. I think it would be interesting to also see if we could do the same thing for 404s. The goal of this change is to make it so that the E2E tests can fail faster (3-4s) than the 30s timeout in the case that something catastrophic happens. As a nice side benefit you get to see the exception message. |
||
|---|---|---|
| .. | ||
| Buffers.MemoryPool | ||
| Buffers.Testing | ||
| CertificateGeneration | ||
| ChunkingCookieManager | ||
| ClosedGenericMatcher | ||
| CopyOnWriteDictionary | ||
| Diagnostics | ||
| E2ETesting | ||
| ErrorPage | ||
| EventSource.Testing | ||
| HttpSys | ||
| ObjectMethodExecutor | ||
| Process | ||
| PropertyActivator | ||
| PropertyHelper | ||
| RangeHelper | ||
| Razor | ||
| RazorViews | ||
| SecurityHelper | ||
| StackTrace | ||
| SyncPoint | ||
| UrlDecoder | ||
| ValueTaskExtensions | ||
| WebEncoders | ||
| test | ||
| NullScope.cs | ||
| ReferenceAssemblyInfo.cs | ||