canonical / canonical/microcloud
Run the `2/stable` system tests using Micro* `x/edge` and `x/candidate` channels
Open
- Dominant language
- Go
- Stars
- 532
- Forks
- 83
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 36
Description
Right now we run the system tests for the `2` track using the latest channels from all the Micro* dependencies.
To catch regressions early on we should schedule some regular tests that also test using the dependency's `x/edge` and `x/candidate` channels.
Contributor guide
Research direction
Start by locating the existing system-test schedule for the `2` track and how it selects the latest Micro* dependency channels. Trace where dependency channels are configured, then determine how regular runs can cover both `x/edge` and `x/candidate`. Done means the scheduled system tests exercise those channels in addition to the current latest-channel tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100