Open xWink opened 8 months ago
Note that this is partially addressed by #510, this removed most blockers that were impacting parallel execution. We may need to adjust a few timings and retries to make this reliable. In the meantime, early adopters can try:
AWS_ACCOUNT_ID=<...> CLUSTER_NAME=<...> CLUSTER_VPC_ID=<...> ginkgo --timeout 90m -v --procs 2 ./suites/...
Currently, running the full e2e test suite takes roughly 50 minutes on my Macbook Pro. This is a consequence of the fact that each test typically takes 1-2 minutes, and we have a large number of tests.
As new e2e tests are added, coverage increases, but test runtime does too.
Possible ways we can improve performance of e2e tests (more ways likely exist):