From 432ff05a3a7ab83bcbb8b7ce4f00179c73b52b76 Mon Sep 17 00:00:00 2001 From: Shai Demri Date: Thu, 12 Oct 2023 14:06:23 +0300 Subject: [PATCH] Update README.md section4.8 add missing content to section 4.8 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 04a5a97fe..ba371d2a9 100644 --- a/README.md +++ b/README.md @@ -802,7 +802,7 @@ b. [Node.js testing - beyond the basics](https://github.com/testjavascript/nodej ## ![✔] 4.8 Use production-like environment for e2e testing -**TL;DR:** End to end (e2e) testing which includes live data used to be the weakest link of the CI process as it depends on multiple heavy services like DB. Use an environment which is as close to your real production environment as possible like a-continue (Missed -continue here, needs content. Judging by the **Otherwise** clause, this should mention docker-compose) +**TL;DR:** End to end (e2e) testing which includes live data used to be the weakest link of the CI process as it depends on multiple heavy services like DB. Use an environment which is as close to your real production environment as possible like docker-compose set up which ensure (1) An easy way ro run the test by anyone, new developers, CI processes etc... (2) A repeatable and isolated running environment so that the outcome of the tests won’t vary depending from where they were run from, (3) Be as close as possible to the production environment. **Otherwise:** Without docker-compose, teams must maintain a testing DB for each testing environment including developers' machines, keep all those DBs in sync so test results won't vary across environments