Skip to main content

Interactivity

tip

UI Coverage is a paid add-on. Schedule a demo today and see how easy it is to enhance your testing while speeding up your development process.

Interactive Elements​

UI Coverage uses a set of rules, based on HTML semantics, WHATWG standards, as well as some additional rules defined by Cypress, to determine which elements are interactive. Some examples of elements that are considered interactive and are thereby included in UI Coverage are:

  • Elements with implicit interactive roles such as elements with a tag of a, button, input, select, textarea, etc.
  • Elements with explicit interactive roles such as elements with a role attribute set to button, checkbox, radio, tab, textbox, etc.
  • Elements with a tabindex attribute set to >= 0.

Interaction Commands​

UI Coverage considers interactive elements "tested" if they are interacted with by a Cypress command. The commands that are considered interactions are:

  • blur
  • check
  • clear
  • click
  • dblclick
  • focus
  • rightclick
  • scrollIntoView
  • scrollTo
  • select
  • selectFile
  • submit
  • trigger
  • type
  • uncheck

UI Coverage tracks links (<a> elements) that haven't been visited during testing. For each untested link, you can see:

Referrers​

The Views containing links to this untested destination. This helps you understand:

  • Where these untested areas are referenced from
  • The navigation paths that could lead to this untested area
  • The context in which these links appear

URLs​

Shows how similar URLs are grouped together. For example, if you have links to /users/1, /users/2, and /users/3, they'll be grouped as /users/*. The URLs section shows all the actual URLs that were grouped together. This is particularly useful for:

  • Understanding the scope of dynamic routes in your application
  • Seeing how many variations of a URL pattern exist
  • Writing configuration rules to handle URL patterns appropriately

Contents