Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shorten the End-to-End test suite execution without reducing coverage #172

Open
pivotaljohn opened this issue Sep 22, 2021 · 0 comments
Open
Labels
priority/unprioritized-backlog Higher priority than priority/awaiting-more-evidence. Contributions are welcome.

Comments

@pivotaljohn
Copy link
Contributor

Describe the problem/challenge you have
It's taking upwards of 20+ minutes for a single E2E run (see test-gh workflow).

This stretches the feedback loop for local development, for CI... it's waste from delays.

Describe the solution you'd like
The faster the better.

This might involve digging in to see where the long lead times are coming from and finding ways to optimize those operations.
Whatever we do, we cannot reduce the confidence we get from running the suite.


Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

@pivotaljohn pivotaljohn added the priority/unprioritized-backlog Higher priority than priority/awaiting-more-evidence. Contributions are welcome. label Sep 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/unprioritized-backlog Higher priority than priority/awaiting-more-evidence. Contributions are welcome.
Projects
Status: To Triage
Development

No branches or pull requests

1 participant