Cypress + Axe testing

[rluders]

Is your feature request related to a problem? Please describe.
I believe that is important for us to have some automated tests. Since we do have the docs pages it should not be complicated to test the behaviors of the components. The test must cover usability and accessibility.

Describe the solution you'd like

• Install Cypress
• Install Axe
• Create at least ONE example test

Describe alternatives you've considered
I don't know any alternative.

Additional context
The Sumé LMS frontend already has those tests on it, maybe it would be easy to just bring them to this repository. Also, there is this guide, that can be useful.

[tulup-conner]

I think Cypress would be fantastic. The Jest DX is inferior, but tests will take longer. Would the plan be to migrate all tests to Cypress? I'm trying to imagine how you would distinguish unit tests from end-to-end in a library like this.

I have day to day experience with Cypress and trying to write unit tests in Jest is making me wish we could just move to Cypress now.

[rluders]

No, we will not migrate any unit test to Cypress. Both have different proposals.

The plan is to use Cypress + Axe to test the components by interacting with Storybook and the Documentation. By doing it we can also check a11y aspects.

PS: Yeah, I know that we could use Cypress to unit test, but... just no.

[tulup-conner]

Ok, what would an example Cypress test actually look like then? I'm a bit confused by that explanation. Would you repeat the behavioral tests of the unit tests, just on the Storybook pages?

Edit: I just want to be able to start writing these so some examples would be nice so I don't go in an undesirable direction with them

[rluders]

Let me give you one scenario:

Test carousel documentation page

• Open the documentation page
• Navigate to the carousel page
• Check if all examples are correctly being rendered
• Check if you can interact with the examples

The idea is to mostly test the components' examples by interacting with them through documentation and storybook, to also assure that our examples are working as expected.

Does it make sense?

This is a very, very, very basic scenario since I'm not QE :)

[tulup-conner]

Yeah that makes perfect sense, you mean to use these purely to test the Storybook/docs pages themselves. I'm silly

[rluders]

'Cause, by doing it, we are also testing our components and it's the desired behavior. Right? :)