Hello, community!
Recently we noticed the following problems with Che DevWorkspace Happy Path test:
- running logic (yaml files/bash scripts) were copied/pasted over repositories.
What makes maintainability bad;
- that was not easy to run happy path test manually against your changes.
The solution we came is to design it in a way:
- possible to run with bash + curl from github;
- don't break target cluster configuration but just tune a bit with needed stuff for test;
A prerequisite for happy path test is Che with DevWorkspaces enabled.
See the following cases to check how to run it locally or as PR check:
Locally:
- deploy Che with DevWorkspaces enabled and then just simply run command which
works better for you:
- if you have che repo -> tests/devworkspace-happy-path/launch.sh
- if you don't have che repo, do the following and it will downloaded into temp dir
PR check:
Nothing special, you need to have Che with DevWorkspace enabled
and then just invoke remote launch, in addition, you may want to bump logs
(since it's temp cluster) with common bash func.
See how it's organized in:
In addition, Maxim is preparing a demo for the upcoming community call.
Anyway thanks Maxim for following the initiative and doing a good job there!
Let us know if you have any ideas on how to make it even easier to use
or you need assistance on setting up it as your repo PR check.
Have a good upcoming weekend!
--
Serhii Leshchenko
principal SOFTWARE ENGINEER
Red Hat
