Repository navigation
[Epic] Regression + E2E testing of Cozystack #759
Description
Activity
Hi, Nick Volynkin (@NickVolynkin). I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.
Issue Summary:
- You proposed adding automated end-to-end regression tests to improve release speed and reliability.
- The focus was on identifying key usage scenarios to cover with these tests.
- Some initial work has been done, as indicated by a related pull request.
- There have been no further updates or discussion on this topic recently.
Next Steps:
- Please let me know if this issue is still relevant to the latest version of cozystack by commenting here.
- If I don’t hear back within 7 days, this issue will be automatically closed.
Thanks for your understanding and contribution!
Superseded by #2847 (the diff-driven & scenario-based E2E testing epic). The scenario-based regression goal is carried forward there, grounded in the current BATS harness (
hack/e2e-apps/), thePackage/PackageSourcemodel, and the diff-driven-install design — broken into concrete, independently-shippable tasks (per-app install scoping, the upgrade scenario from #2401, and the install smoke scenario). Closing this older epic in favor of the design-driven one.Reacted by Nick Volynkin
We want to have regular automated testing of Cozystack on end-to-end scenarios, so that we could make releases faster and be more confident in them.
The goal is to cover major usage scenarios (the list of which we must define along the way).