Cypress tests struggle to assert clipboard and exact rendered text
Cypress users want to verify copied text and compare rendered text exactly, but the reports describe trouble accessing clipboard contents and brittle or awkward text assertions. Stubbing a clipboard call may not verify legacy copy behavior, while substring checks can pass for the wrong value and exact checks can be sensitive to whitespace. These signals date from 2018–2020, so current Cypress and browser support should be validated before building.
For frontend developers writing Cypress tests. Mentioned from Jul 2018 to Nov 2020 on GitHub.
4 different people described this problem in 2 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.2/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Low
What people said
Quoted word for word. Follow a link to read the whole discussion.
There is no way to access the clipboard in a test, as far as I can tell. Desired behavior: There should be an easy way to test what the clipboard holds
This is what that looks like when implemented in Typescript: Note that this approach doesn't solve every problem. For example, if you use the invisible textarea workaround (for older browsers), I still don't know of any way to assert about the actual content of the system clipboard
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 3 places to find your first customers
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks