-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Che Smoke Test PR check for Che-Code repository #21789
Comments
@azatsarynnyy : there is a plan to switch existed Che-Theia Happy path tests to VS Code Editor using https://github.com/redhat-developer/vscode-extension-tester library: #21463 PR: #21684 |
I have changed the title to reflect that we want to run a smoke test rather than an happy path test. |
There is Che-Code editor smoke test available for running: https://github.com/eclipse/che/blob/main/tests/e2e/specs/SmokeTest.spec.ts Here an example of usage: https://github.com/eclipse-che/che-operator/blob/main/build/scripts/oc-tests/oc-test-happy-path.sh |
https://github.com/eclipse-che/che-operator/blob/main/build/scripts/oc-tests/oc-test-happy-path.sh is the script to run smoke test on OpenShift CI - an alternative to GitHub Actions where minikube is available for deploy Eclipse Che to only. There are also GitHub Actions to deploy Eclipse Che to minikube [1], but I am not sure if there is enough resources in there to start Eclipse Che workspace with VS Code Editor on board. [1] https://github.com/che-incubator/?q=action&type=all&language=&sort= |
Is your task related to a problem? Please describe
Currently, there're PR checks in the Che-Code repository that run the upstream tests. But there's no PR check that would run the Happy Path tests for testing Che-specific functionality. So, the developer needs to check by hand if they didn't break anything Che-specific.
Describe the solution you'd like
Need to add a PR check that would run Happy Path Tests against the opened PR. It should be a required check to prevent merging the code introduces some regression.
Additional context
The text was updated successfully, but these errors were encountered: