[patch]- Remove High Maintenance- Not suitable to FVT category Tests #1489
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
Remove High Maintenance Tests
chiragcsatani
requested review from
durera,
JonahLuckett,
andrercm,
sanjayprab,
terenceq,
whitfiea and
alequint
as code owners
alequint
approved these changes
Mar 3, 2025
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.
Remove High Maintenance Tests:
we have decided to remove these 3 tests which are giving high maintenance.
base-ui-mas-navigation
Reason: Test includes lot of UI navigations which depends upon availability of apps and many features are being tested at one part of test. Test never passed due to the time it takes to execute. more then 1 hr. Test is good candidate for Regression.
base-ui-sec-inactive-auth
Reason: This is negative test where user is to be inactivated and then verify user is inactivated or NOT. Test is likely to impact other tests due to inactivity of user and failing intermittently on behaviour and timing issue. Test is more applicable to regression suite instead FVT.
fvt-manage-application-designer
Reason: Test never worked in pipeline since its onboard to FVT due to Selenium tekton issue. Test works okay in local. Attempt to make it stable in pipeline is in progress. until then removing from FVT.