cypress-documentation

cypress-documentation copied to clipboard

Subject

Component testing

Description

Within the CT overview page we can be more clear about how component testing works and what it does.

In "Why Component Testing?" we mention "And since this is Cypress, you get the same APIs, plugins, and ecosystem you are used to with end-to-end testing to create component tests." but this is not helpful for people who are new to Cypress itself as a tool.

We should mention explicitly the relevant kinds of things that are possible in Cypress which are relevant to component testing and might be familiar from other unit/component testing solutions.

Another example that we could improve is the opening sentence "Cypress Component Testing provides a component workbench for you to quickly build and test components from multiple front-end UI libraries — no matter how simple or complex."

This is true but we can build a bit on the "component workbench" idea and make sure it is clear from the start that this all happens in the browser and emphasizes a great and fast DX.

This page definitely needs some love. It was the only one that wasn't revisited from Cypress Beta to GA.