-
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
Implement CheCode Editor POC test #21684
Implement CheCode Editor POC test #21684
Conversation
@ScrewTSW : could you, please, write about how to run the test, and give an example of test run? |
1ee769e
to
2aa6d32
Compare
@ScrewTSW : commented code could be removed having commit history. It could also be useful to have list of tests which needs to be rewritten to be run in VS Code Editor, e.g. tests/e2e/tests/e2e/GitPublishBranch.spec.ts |
try { | ||
await driverHelper.getDriver().wait(until.elementLocated(By.className('monaco-workbench'))); | ||
} catch (err) { | ||
if ((err as Error).name === 'WebDriverError') { |
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.
It's interesting to know which kind of 'WebDriverError' is handled by 3 seconds wait.
Can it be handled by adding timeout to command in try {} block? :
await driverHelper.getDriver().wait(until.elementLocated(By.className('monaco-workbench')), 3000);
2aa6d32
to
9252481
Compare
@ScrewTSW: is there a draft of e2e/tests/e2e_happy_path/vscode/HappyPath.spec.ts ready to run? |
No, not yet. This is just POC refactor, so that it's ready for additional implementations |
I see. Actually, what has already been done looks commonly good. |
77f0828
to
70b84e1
Compare
If it's shot name for |
test('Register running workspace', async () => { | ||
CheReporter.registerRunningWorkspace(WorkspaceHandlingTests.getWorkspaceName()); | ||
}); | ||
test('Wait workspace readiness', async() => { |
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.
What is the criteria of workspace readiness?
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.
The objects are present ant accessible. It's just a POC
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.
It would be nice to express it in the test log, to understand which UI elements are expected to appear to say "Workspace is ready".
tests/e2e/tests/e2e_happy_path/theia/DevWorkspaceHappyPath.spec.ts
Outdated
Show resolved
Hide resolved
70b84e1
to
eec3855
Compare
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.
Looks good to merge.
eec3855
to
d730113
Compare
Signed-off-by: Tibor Dancs <[email protected]>
…ng monaco-page-objects Signed-off-by: Tibor Dancs <[email protected]>
….json Signed-off-by: Tibor Dancs <[email protected]>
Signed-off-by: Tibor Dancs <[email protected]>
…avaSpringBoot theia test. refactored WorkspaceHandlingTests to be universal Signed-off-by: Tibor Dancs <[email protected]>
Signed-off-by: Tibor Dancs <[email protected]>
Signed-off-by: Tibor Dancs <[email protected]>
Signed-off-by: Tibor Dancs <[email protected]>
e11fca5
to
e91d4c3
Compare
What does this PR do?
Screenshot/screencast of this PR
What issues does this PR fix or reference?
https://issues.redhat.com/browse/CRW-3107
#21789
How to test this PR?
TS_SELENIUM_BASE_URL
TS_SELENIUM_USERNAME
TS_SELENIUM_OCP_USERNAME
TS_SELENIUM_PASSWORD
TS_SELENIUM_OCP_PASSWORD
TS_OCP_LOGIN_PROVIDER_TITLE
TS_SELENIUM_VALUE_OPENSHIFT_OAUTH="true"
initDefaultValues.sh
npm run test-java-springboot
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.