[Test] Fix WebTerminal e2e tests #23271
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SkorikSergey
added
status/code-review
SkorikSergey
requested review from
musienko-maxim and
dmytro-ndp
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
We need to fix WebTerminalUnderRegularUser and WebTerminalUnderAdmin e2e test for using them in WTO pre-release automation.
WebTerminalUnderRegularUser test fails because web element to visible. Scrolling fix this problem.
For WebTerminalUnderAdmin test expected tool list should be fixed.
What issues does this PR fix or reference?
https://issues.redhat.com/browse/CRW-7859
How to test this PR?
Start e2e tests as usual except it is need to change
TS_SELENIUM_OCP_USERNAMEto user name:export TS_SELENIUM_OCP_USERNAME="user"for WebTerminalUnderRegularUserexport TS_SELENIUM_OCP_USERNAME="admin"for WebTerminalUnderAdminPR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or referenceandHow to test this PRcompletedReviewers
Reviewers, please comment how you tested the PR when approving it.