mirror of
https://github.com/angular/angular.git
synced 2026-09-14 13:54:52 +08:00
198e64ab75
Prior to this commit, `TestBed` would require tests call `flushEffects` or `fixture.detectChanges` in order to execute effects. In general, we want to discourage authoring tests like this because it makes the timing of change detection and effects differ from what happens in the application. Instead, developers should perform actions and `await` (or `flush`/`tick` when using `fakeAsync`) some `Promise` so that Angular can react to the changes in the same way that it does in the application. Note that this still _allows_ developers to flush effects synchronously with `flushEffects` and `detectChanges` but also enables the <action>, `await` pattern described above. PR Close #53843
API Examples
This folder contains small example apps that get in-lined into our API docs. Each example contains tests for application behavior (as opposed to testing Angular's behavior) just like an Angular application developer would write.
Running the examples
# Serving individual examples (e.g. common)
yarn bazel run //packages/examples/common:devserver
# "core" examples
yarn bazel run //packages/examples/core:devserver
Running the tests
yarn bazel test //packages/examples/...