Centralize DevWorkspace Happy Path test #20421
Labels
area/qe
engine/devworkspace
Issues related to Che configured to use the devworkspace controller as workspace engine.
kind/task
Internal things, technical debt, and to-do tasks to be performed.
sprint/current
Milestone
Is your task related to a problem? Please describe
The problem is that currently there are 3 targets for DevWorkspace Happy path test run by Prow:
And they duplicate some resources, which means - when you need to fix some even minor stuff, like devfile/project which should be used for testing, you need to propagate it to all consumers.
Describe the solution you'd like
Setting up the infrastrucure (deploying Che, DWO) is on consumer side, but tests logic - how to run it, which image to use, which devfile to use should be centralized somehow.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: