search

open-sauced / hot

🍕The site that recommends the hottest projects on GitHub.
https://hot.opensauced.pizza
MIT License
418 stars 145 forks source link

Feature: End to end testing tracking issue #403

Open bdougie opened 1 year ago

bdougie commented 1 year ago

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 - https://github.com/open-sauced/hot/pull/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.

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

Contributing Docs

0-vortex commented 1 year ago

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

NsdHSO commented 1 year ago

@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 commented 1 year ago

@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 🔥