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

[SPIKE] Determine a better solution for running smoke tests on staging #16350

Open
2 tasks
chris-kuryak opened this issue Oct 25, 2024 · 0 comments
Open
2 tasks
Labels
engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team needs-refinement Tickets that need refinement from the team

Comments

@chris-kuryak
Copy link
Collaborator

Problem statement

The current smoke tests in staging run during deployment, which blocks deployment if something goes wrong. This is not ideal as smoke tests should be pre-emptive and allow time to fix issues before deployment. Therefore, we need to find a better solution for when and how to run smoke tests in staging.

What you need to know

Acceptance criteria

Propose and document a solution that:

  • Allows errors from Smoke Tests to be caught and report to FE engineers at least 24 hours before deployment
  • Smoke tests are performed automatically and regularly without much (if any) human input
@chris-kuryak chris-kuryak added engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team needs-refinement Tickets that need refinement from the team labels Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering Work to be completed by an engineer experience Team label to flag issues owned by the Experience Team needs-refinement Tickets that need refinement from the team
Projects
None yet
Development

No branches or pull requests

1 participant