Repository navigation
[Feature] Define smoke and integration scopes for Kubernetes runs #779
Description
Define a stable VIP marker contract for selecting Kubernetes smoke and integration scenarios without conflating them with VIP's containerized CI suites.
Affected area
Other / not sure
What problem are you trying to solve?
The images-build workflow currently selects only smoke scenarios, while broader scenarios may depend on product configuration or seeded state. Selecting all tests by default would run scenarios without their required environment and could produce misleading skips or failures.
Proposed solution
Audit the current VIP markers and agree which scenarios are suitable for the Kubernetes smoke scope versus a bounded integration scope. Keep smoke fast and independent of seeded state; document integration prerequisites and make its selection explicit. Keep this scope contract distinct from the containerized CI coverage tracked in VIP's existing CI work.
Acceptance criteria:
- The intended smoke and Kubernetes integration scenario sets are documented.
- The existing marker/selection mechanism can select each set independently and predictably.
- Tests that require bootstrapped product state are not selected as smoke tests.
Alternatives considered
Selecting every product test for integration runs would couple the workflow to unrelated categories and environment assumptions; selecting tests by ad hoc name filters would be difficult to maintain.
Related:
Activity