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.

Sign up for GitHub

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

Jump to bottom

Reduce E2E Test Runtime #697

Closed
jalling97 opened this issue Jul 1, 2024 · 0 comments · Fixed by #808
Closed

Reduce E2E Test Runtime #697

jalling97 opened this issue Jul 1, 2024 · 0 comments · Fixed by #808
Assignees
@jalling97
Labels
spike tech-debt Not a feature, but still necessary

Comments

@jalling97
Copy link
Contributor

Describe what should be investigated or refactored

The e2e.yaml workflow takes ~60 minutes to run fully and is slowing down development time. The tests should be refactored to reduce runtime.

Additional context

Potential options include:

  • Splitting the e2e test into multiple workflows (each would have some replicated work, but this could help parallelize some of the steps)
  • Run certain steps in parallel within the same workflow (e.g some package deployments can possibly be run at the same time)
@jalling97 jalling97 added the tech-debt Not a feature, but still necessary label Jul 1, 2024
@jalling97 jalling97 self-assigned this Jul 1, 2024
@jalling97 jalling97 added the spike label Jul 1, 2024
@jalling97 jalling97 linked a pull request Jul 22, 2024 that will close this issue
chore: split e2e.yaml into multiple workflows #808
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jalling97 jalling97

Labels
spike tech-debt Not a feature, but still necessary
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: split e2e.yaml into multiple workflows defenseunicorns/leapfrogai
1 participant
@jalling97