Feature: End to end testing tracking issue

[bdougie]

Type of feature

✅ Test

Current behavior

While chatting with @JoshuaKGoldberg yesterday and discussing an approach for end-to-end testing of this app. I will use this as a tracking issue for setting up end to end testing with Cypress, now that testing works, sort of - #400.

Suggested solution

Feature Testing plan

So far, we are testing logged in/out users. The following features will also need tests for functionality with a lens on accessibility.

• e2e testing: repo submissions #411
• e2e testing: filtering repos #412
• e2e testing: paginations of repos #413
• e2e testing: searching Repos #414

Additional context

End-to-end testing is conducted through Cypress. Here is a guide - https://docs.cypress.io/guides/end-to-end-testing/writing-your-first-end-to-end-test

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs

[0-vortex]

Currently using puppeteer but the action implementation has been lagging, tho I don't mind switching to cypress! 🍕

[NsdHSO]

@0-vortex , @bdougie what should I use to make E2e test? puppeteer | cypress? I have this ticket #414, and I saw a ticket about accessibility. I should wait until it is finished #418?

[0-vortex]

@0-vortex , @bdougie what should I use to make E2e test? puppeteer | cypress? I have this ticket #414, and I saw a ticket about accessibility. I should wait until it is finished #418?

I know you asked about this in discord as well, putting this here for reference: as per #395 we are using https://playwright.dev 🔥