8a5eb08672
Closes #10503 It is possible for code in `beforeEach` to capture and fork a zone (for example creating `NgZone` in `beforeEach`). Subsequently the code in `it` may chose to do `fakeAsync`. The issue is that because the code in `it` can use `NgZone` from the `beforeEach`. it effectively can escape the `fakeAsync` zone. A solution is to run all of the test in `ProxyZone` which allows a test to dynamically replace the rules at any time. This allows the `beforeEach` to fork a zone, and then `it` to retroactively became `fakeAsync` zone. |
||
|---|---|---|
| .. | ||
| @angular | ||
| angular1_router | ||
| benchmarks | ||
| benchmarks_external | ||
| benchpress | ||
| e2e_util | ||
| payload_tests/hello_world/ts | ||
| playground | ||
| rollup-test | ||
| empty.ts | ||
| es6-subset.d.ts | ||
| system.d.ts | ||
| tsconfig.json | ||
| types.d.ts | ||