Skip to content

Commit c8b7861

Browse files
committed
fix: add newline back in
1 parent 80dc62b commit c8b7861

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

content/fundamentals/unit-testing.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -184,6 +184,7 @@ describe('CatsController', () => {
184184
```
185185

186186
You can also retrieve these mocks out of the testing container as you normally would custom providers, `modRef.get(CatsService)`.
187+
187188
#### End-to-end testing
188189

189190
Unlike unit testing, which focuses on individual modules and classes, end-to-end (e2e) testing covers the interaction of classes and modules at a more aggregate level -- closer to the kind of interaction that end-users will have with the production system. As an application grows, it becomes hard to manually test the end-to-end behavior of each API endpoint. Automated end-to-end tests help us ensure that the overall behavior of the system is correct and meets project requirements. To perform e2e tests we use a similar configuration to the one we just covered in **unit testing**. In addition, Nest makes it easy to use the [Supertest](https://github.com/visionmedia/supertest) library to simulate HTTP requests.

0 commit comments

Comments
 (0)