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

reduce number of steps in e2e happyPath #1178

Closed
Tracked by #877
MSalopek opened this issue Aug 2, 2023 · 0 comments · Fixed by #1181
Closed
Tracked by #877

reduce number of steps in e2e happyPath #1178

MSalopek opened this issue Aug 2, 2023 · 0 comments · Fixed by #1181
Assignees
Labels
scope: testing Code review, testing, making sure the code is following the specification. type: tech-debt Slows down development in the long run

Comments

@MSalopek
Copy link
Contributor

MSalopek commented Aug 2, 2023

At present, happyPath e2e tests have ~ 50 steps, some of which are duplicates. This causes the happyPath e2e tests to run for >20min on the CI.

Since happyPath runs on every commit, the number of steps should be reduced by removing duplicate test cases.

@MSalopek MSalopek self-assigned this Aug 2, 2023
@MSalopek MSalopek added scope: testing Code review, testing, making sure the code is following the specification. type: tech-debt Slows down development in the long run labels Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: testing Code review, testing, making sure the code is following the specification. type: tech-debt Slows down development in the long run
Projects
Status: ✅ Done
1 participant