Adding IDs for Operator tests #1599
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.
Fixes https://github.com/miniohq/engineering/issues/534
I am preparing all CSS selectors for Operator tests.
It is easier to click or text over an element when is easy to find.
In most cases, CSS selector can be created with current attributes like:
But in other cases, this is just not possible, and I was having my mind in Python/Selenium where Xpath Selectors were used in my other projects, I read a bit on XPATH in TestCafe and found some repos... Nevertheless, since our React architecture allow id additions, then I found this approach easier for now. Later in the future we can re-evaluate and see if we should rather use xpath selectors or keep improving our DOM Attributes.