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

[Task] Update upgrade E2E test to run a series of upgrades rather than a single version #13062

Open
9 tasks
sethkfman opened this issue Jan 17, 2025 · 0 comments
Open
9 tasks

Comments

@sethkfman
Copy link
Contributor

What is this about?

This ticket is meant to update the E2E upgrade test to include more legacy versions and have the automation upgrade through multiple versions. The issue below could have been detected if there was an upgrade test from 7 versions prior. Here is Mixpanel data to support upgrade version decision.

Related Issue: #12207
Fix: #12219

Scenario

No response

Design

No response

Technical Details

No response

Threat Modeling Framework

No response

Acceptance Criteria

No response

Stakeholder review needed before the work gets merged

  • Engineering (needed in most cases)
  • Design
  • Product
  • QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
  • Security
  • Legal
  • Marketing
  • Management (please specify)
  • Other (please specify)

References

https://docs.google.com/document/d/1hOPiaJBT64ydkRSZ9twY0kT6DUJ36lcE6RLbtpbWQ-w/edit?tab=t.0#bookmark=id.9c1gz7am7yv

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant