[Epic] Regression + E2E testing of Cozystack #759

Activity

1. Nick Volynkin (NickVolynkin)

   added the

   Feature

   issue type on Apr 6, 2025
2. Nick Volynkin (NickVolynkin)

   added

   epicA large development increment that brings definite value to Cozystack usersA large development increment that brings definite value to Cozystack users

   on Apr 6, 2025
3. Nick Volynkin (NickVolynkin)

   added sub-issues on Apr 8, 2025

   • DockerHub quota exceeded in CI #760
   • Enable tests to run in parallel #761
   • Add simple test with kind #98
   • Enable CI to work with registry on fork-based PRs #763
   • Configure GitHub CI #71
4. dosubot commented on Oct 17, 2025

   

   dosubotbot

   on Oct 17, 2025 – with DosuBot

   More actions

   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!
5. dosubot

   added

   lifecycle/staleDenotes an issue or PR has remained open with no activity and has become staleDenotes an issue or PR has remained open with no activity and has become stale

   on Oct 17, 2025
6. myasnikovdaniil commented on Jun 8, 2026

   

   myasnikovdaniil

   on Jun 8, 2026

   Contributor

   More actions

   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/), the Package/PackageSource model, 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.

   👍React with 👍1Reacted by Nick Volynkin
7. myasnikovdaniil

   closed this as completedon Jun 8, 2026