- We used to have this via PHPUnit on the Beta Cluster, but it flaked and we switched it off.
- We also used to have e.g. the AppArmor tests, but had to disable them.
- We re-enabled it as mock tests, testing the integration of the various WF components together, but now we're not testing that these mocks are actual reality.
- We should re-establish these tests (or something like them) as a suite of end-to-end tests.
- They shouldn't be browser tests (which are slow and flaky); we have those already, these should just hit the API.
- For some paths, e.g. the AppArmor ones, they may need to be authenticated as a user.
- Let's add this suite to the helm chart's test command for AW CI?
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
@gengh: This hasn't been triaged yet. Also, it's definitely not waiting for Gregory, is it?
Comment Actions
Re-prioritising to Medium during an Engineering Backlog triage. The gap this card describes (e2e API-level coverage end-to-end through MW API → orchestrator → evaluator → back, vs. mock-based integration tests that can't catch drift) is real and unresolved. But 13 months of no movement, and an unanswered poke to gengh in April 2025, tells me High wasn't actually driving action; Medium is the honest signal. Cross-reference: T343378 (now In Progress / Medium) is a narrow tactical slice that wires the existing AppArmor PHPUnit suite into aw-ci-chart's CI via MR 27 — that lands a quick AppArmor-coverage win in the current chart, but doesn't replace this card's broader Catalyst-hosted e2e vision. When this is picked up, the first decision will be where it actually lives (Catalyst-hosted suite per the current title, or a continuation of the helm-chart pattern); please record that decision here so it's discoverable.