Please add ID/data-testid on every element requires user interaction

[mmelko]

This is a...

[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

• Menu links done

Dashboard:

• All buttons/links (Create integration, View all integrations, Create connections, view all connections)
• integration list elements in Top 5 integrations - data-testid should contain integration name if possible.
• Buttons/links within integration item
• Connection card (link)
• Connection card tittle
• Recent updates - integration item - data-testid should contain integration name if possible.

Integrations page

• all buttons/links
• Items in integration list - data-testid should contain integration name if possible.
• links within itegration item

integration details

• all links/buttons

Integration editor

• integration-flow steps
• connection cards
• Integration editor buttons (Create connection, cancel .. )
• Connection action list item
• Dropdown menus that aren't <select> tags (i.e Period time units)
• Configuration action buttons (Choose action, Next)
• Configuration action inputs (mostly done)

Connections page

• Buttons
• Connection cards (only tittles are)
• heading tech-preview
• Kebab menus
• Connector cards
• Connection configuration inputs
• Connection configuration buttons

Settings

• Oauth item heading

In summary: all buttons, inputs, links, headings bodies, menus :)

[gashcrumb]

Awesome, thanks for the checklist, that's probably most of the work right there 👍

[gashcrumb]

for the codemirror instance on the describe data page I wound up having to just put an ID on the containing div.