From 99a18287c163e328f87709cb224742ccac3e113a Mon Sep 17 00:00:00 2001 From: David Cho-Lerat Date: Sun, 12 Jan 2020 06:09:23 +0100 Subject: [PATCH] Update testing-environments.md (#2665) Remove extraneous "both" --- content/docs/testing-environments.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/testing-environments.md b/content/docs/testing-environments.md index 5120a4f6..d77e76f4 100644 --- a/content/docs/testing-environments.md +++ b/content/docs/testing-environments.md @@ -53,6 +53,6 @@ Sometimes, you may not want to mock timers. For example, maybe you're testing an ### End-to-end tests {#end-to-end-tests-aka-e2e-tests} -End-to-end tests are useful for testing longer workflows, especially when they're critical to your business (such as payments or signups). For these tests, you'd probably want to test both how a real browser renders the whole app, fetches data from the real API endpoints, uses sessions and cookies, navigates between different links. You might also likely want to make assertions not just on the DOM state, but on the backing data as well (e.g. to verify whether the updates have been persisted to the database). +End-to-end tests are useful for testing longer workflows, especially when they're critical to your business (such as payments or signups). For these tests, you'd probably want to test how a real browser renders the whole app, fetches data from the real API endpoints, uses sessions and cookies, navigates between different links. You might also likely want to make assertions not just on the DOM state, but on the backing data as well (e.g. to verify whether the updates have been persisted to the database). In this scenario, you would use a framework like [Cypress](https://www.cypress.io/) or a library like [puppeteer](https://github.com/GoogleChrome/puppeteer) so you can navigate between multiple routes and assert on side effects not just in the browser, but potentially on the backend as well.