Splitting Operator UI Tests for faster execution #2366
Merged
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.
Objective:
To make
Operator UI Testsrun faster and more reliable.Story:
Currently, there are two main tests:
login.tstenants.tsThey depend on different libraries, which is ok, not the main point to change here.
But I am going to group them in different folders, letting main
uitls.tsbe on top of them in case other tests are added in the future.Additional Information:
This is going to make it just a bit faster. What is actually consuming lot of time here is the setup of the cluster with Operator and Tenant; not testcafe itself. But this is just the first PR. In my next PR, I will focus on the k8s side to see if we can actually decrease the time we consume in creating the cluster.
For reliability, I noticed that some marks render slower than the expected result, added some waits around them to let page to render prior checking on them, hopefully this will increase the reliability of our tests.
Re-org:
Results: