Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upE2E Tests: Add CPU/Network slowdown configuration options #18770
Conversation
Thank you for working on it. It's a bit simplified implementation in comparison to what I proposed in the original issue but it should be enough for us to simulate those specific configurations. One day, I will implement it as advertised in smooth-code/jest-puppeteer#241 directly in the Based on the code from the issue and this implementation. I'm confident it's good to go. I can give it a spin once it's merged into |
Co-Authored-By: Grzegorz (Greg) Ziółkowski <grzegorz@gziolo.pl>
This comment has been minimized.
This comment has been minimized.
Yeah, at least for how I expected it to work, this would be sufficient for one-off debugging. I see it as similar to running "headless" or "slowmo" in that way, so modeled it after those options. |
aduth commentedNov 26, 2019
Closes #15677
This pull request seeks to add additional environment variable configuration options to the E2E test runner which can be used to simulate slow network or CPU conditions.
For more information, see included Testing Overview document description:
Testing Instructions:
You can observe that by providing a
THROTTLE_CPU
value when runningnpm run test-e2e
for a test suite, it will likely take longer to complete than if the value is not provided.