You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 18, 2021. It is now read-only.
Since we're planning to use the jurassic.ninja service to create fresh Jetpack sites for testing, it's worth to think about some optimization of the total test execution time. Currently, creating one of those sites takes around 30 secs.
It would be nice if we create and maintain a list of ready-to-use fresh jurassic.ninja sites (for example 20 of them). So every time a test needs a new Jetpack site, it pulls the oldest one from the list, removes it from the list, and initiates the creation of a new one.
This could help us reduce a large portion of the execution time for running Jetpack-related e2e tests.
Since we're planning to use the
jurassic.ninja
service to create fresh Jetpack sites for testing, it's worth to think about some optimization of the total test execution time. Currently, creating one of those sites takes around 30 secs.It would be nice if we create and maintain a list of ready-to-use fresh
jurassic.ninja
sites (for example 20 of them). So every time a test needs a new Jetpack site, it pulls the oldest one from the list, removes it from the list, and initiates the creation of a new one.This could help us reduce a large portion of the execution time for running Jetpack-related e2e tests.
cc @oskosk @seear @sirreal
The text was updated successfully, but these errors were encountered: