From aea06d8c044624e277d7ca21ca4470acd6789e02 Mon Sep 17 00:00:00 2001 From: Ulrich Pogson Date: Thu, 23 Jun 2022 14:15:29 +0200 Subject: [PATCH] Add an explanation how to setup environment to do run the performance test (#41883) --- docs/contributors/code/testing-overview.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/docs/contributors/code/testing-overview.md b/docs/contributors/code/testing-overview.md index 21dbb4ddd9b1d8..1ddab1cfd1a778 100644 --- a/docs/contributors/code/testing-overview.md +++ b/docs/contributors/code/testing-overview.md @@ -604,7 +604,17 @@ To ensure that the editor stays performant as we add features, we monitor the im - The time it takes for the browser to respond when typing. - The time it takes to select a block. -Performance tests are end-to-end tests running the editor and capturing these measures. To run the tests, make sure you have an e2e testing environment ready and run the following command: +Performance tests are end-to-end tests running the editor and capturing these measures. Make sure you have an e2e testing environment ready. + +To set up the e2e testing environment, checkout the Gutenberg repository and switch to the branch that you would like to test. Run the following command to prepare the environment. + +``` +nvm use && npm install +npm run build:packages +npm run wp-env start +``` + +To run the tests run the following command: ``` npm run test-performance