[x] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Documentation issue or request
Description
Currently test-suite depends heavily on pattern-fly-classes selectors. It'd be nice if every page fragment (for user interaction) could have id or data-testid attribute.
For example:
Navigation
[x] Menu links done
Dashboard:
[x] All buttons/links (Create integration, View all integrations, Create connections, view all connections)
[x] integration list elements in Top 5 integrations - data-testid should contain integration name if possible.
[x] Buttons/links within integration item
[x] Connection card (link)
[x] Connection card tittle
[ ] Recent updates - integration item - data-testid should contain integration name if possible.
Integrations page
[x] all buttons/links
[x] Items in integration list - data-testid should contain integration name if possible.
This is a...
Description
Currently test-suite depends heavily on pattern-fly-classes selectors. It'd be nice if every page fragment (for user interaction) could have id or data-testid attribute.
For example:
Navigation
Dashboard:
[ ] Recent updates - integration item - data-testid should contain integration name if possible.
Integrations page
integration details
Integration editor
<select>
tags (i.e Period time units)Connections page
Settings
In summary: all buttons, inputs, links, headings bodies, menus :)