-
Notifications
You must be signed in to change notification settings - Fork 182
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
[QA] WebUITests fails while asserting breadcrumb visibility #7385
Labels
Comments
PrajwolAmatya
changed the title
[QA] WebUITests fails while asserting breadcrum visibility
[QA] WebUITests fails while asserting breadcrumb visibility
Sep 29, 2023
Since there are some changes to webconfig file in this PR #7369, should we remove the following scenario or not? @ScharfViktor @saw-jan @kobergj Scenario: Check breadCrumb for home folder
Given the property "homeFolder" of "options" has been set to "/0" in web config file
And user "Alice" has logged in using the webUI
Then breadcrumb for folder "0" should be displayed on the webUI |
Since now we cannot update the web config during the test execution, I would vote to remove the scenario and the step defs. // tests/acceptance/stepDefinitions/generalCntext.js
the property {string} has been set to {string} in web config file
the property {string} of {string} has been set to {string} in web config file
the property {string} of {string} has been set to true in web config file
the property {string} of {string} has been set to false in web config file
the property {string} of {string} is changed to true in web config file
the property {string} of {string} is changed to false in web config file
the property {string} has been deleted in web config file |
Merged
9 tasks
9 tasks
Need to have a web bump in ocis |
web bump ready in #7404 |
web bump is done and webUI test pipelines are all green. Closing here |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Multiple builds failing in breadCrumb.feature
Builds:
The text was updated successfully, but these errors were encountered: