Closed musienko-maxim closed 1 month ago
@musienko-maxim : the test seems to be the translation of ApiTest_Php.groovy Jenkins script to the typescript, which looks like a step back compare to the another approach which was implemented in the https://github.com/eclipse-che/che/blob/main/tests/e2e/specs/api/DevfileAcceptanceTestAPI.spec.ts, when we are taking commands to execute from devworkspace configuration (see the issue https://github.com/eclipse-che/che/issues/21514). It is also adding one more layer - javascript - to the test execution, which makes the test less reliable and more complex when run using Jenkins test pipeline.
It was actually expected to see fixed https://github.com/eclipse-che/che/blob/main/tests/e2e/specs/api/DevfileAcceptanceTestAPI.spec.ts script, to get devworkspace configuration from dashbaord API, not from devfile registry. Sample name to test could be defined by environment variable TS_SELENIUM_DASHBOARD_SAMPLE_NAME
.
@musienko-maxim : after the call with you I have changed my mind and think that this approach could also be applied, even though it will be a big chunk of work to write test for each devfile sample separately.
Let's try it on Jenkins CI: https://main-jenkins-csb-crwqe.apps.ocp-c1.prod.psi.redhat.com/job/Testing/job/e2e/job/basic/job/typescript-tests/28674/
It would also be great to finish clean up of devfile registry specific code carefully, like DevfilesRegistryHelper
to rename to DevfilesHelper
What does this PR do?
This PR provides an alternative solution for API tests using our CHE test codebase:
Screenshot/screencast of this PR
What issues does this PR fix or reference?
https://issues.redhat.com/browse/CRW-7539
How to test this PR?
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or reference
andHow to test this PR
completedReviewers
Reviewers, please comment how you tested the PR when approving it.