-
Notifications
You must be signed in to change notification settings - Fork 99
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
Create new E2E selenium test module on TypeScript #168
Conversation
Create e2e test to install CodeReady Workspaces by using OperatorHub UI Create needed page objects Modify .gitignore file
crw_stable-branch_PR # 127: SUCCESS |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@artaleks9 : we could probably avoid duplication of upstream Che E2E tests by taking into consideration next approach https://github.com/redhat-developer/rh-che/tree/master/e2e-saas
…aces into crw-223
crw_stable-branch_PR # 128: SUCCESS |
crw_stable-branch_PR # 129: SUCCESS |
…aces into crw-223
crw_stable-branch_PR # 132: SUCCESS |
ci-test |
Results of automated E2E tests of Codeready on OCP: FAILURE |
ci-test |
ci-test-okd |
Results of automated E2E tests of Codeready on OCP: FAILURE |
Results of automated E2E tests of Codeready on OKD: FAILURE |
|
What does this PR do?
What issues does this PR fix or reference?
https://issues.jboss.org/browse/CRW-223