cargdev/angular
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: fix typo if FAQ section (#24210)

Browse Source 
closes #22360

PR Close #24210
This commit is contained in:
Vani 2018-04-06 10:47:38 -07:00 committed by Victor Berchet
parent 3b9c5c849c
commit 4247176b6e
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
aio/content/guide/testing.md
View File

@ -3378,11 +3378,11 @@ next to their corresponding helper files.
{@a q-e2e} {@a q-e2e}
#### Why not rely on E2E tests of DOM integration? #### Why not rely on E2E tests of DOM integration?
The component DOM tests describe in this guide often require extensive setup and The component DOM tests described in this guide often require extensive setup and
advanced techniques where as the [class-only test](#component-class-testing) advanced techniques whereas the [unit tests](#component-class-testing)
were comparatively simple. are comparatively simple.
Why not defer DOM integration tests to end-to-end (E2E) testing? #### Why not defer DOM integration tests to end-to-end (E2E) testing?
E2E tests are great for high-level validation of the entire system. E2E tests are great for high-level validation of the entire system.
But they can't give you the comprehensive test coverage that you'd expect from unit tests. But they can't give you the comprehensive test coverage that you'd expect from unit tests.