test: setup cypress e2e tests

[diivi]

Description

#238

What type of PR is this? (check all applicable)

• 🍕 Feature
• 🐛 Bug Fix
• 📝 Documentation Update
• 🎨 Style
• 🧑‍💻 Code Refactor
• 🔥 Performance Improvements
• ✅ Test
• 🤖 Build
• 🔁 CI
• 📦 Chore (Release)
• ⏩ Revert

Related Tickets & Documents

#238

Mobile & Desktop Screenshots/Recordings

Added tests?

• 👍 yes
• 🙅 no, because they aren't needed
• 🙋 no, because I need help

Added to documentation?

• 📜 README.md
• 📓 docs.opensauced.pizza
• 🍕 dev.to/opensauced
• 📕 storybook
• 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

[diivi]

https://github.com/open-sauced/ai/actions/runs/5763232402/job/15624620494?pr=239#step:6:58

Should I run the build job before the test job?

[Anush008]

Should I run the build job before the test job?

That seems to be the reason why the e2e test has failed. Because its unable to find the extension build.

We should probably run vitest first, followed by a build and then the e2e tests.

[diivi]

We should probably run vitest first, followed by a build and then the e2e tests.

That's not possible with the current workflow setup (it just runs npm run test), so I'll move build up.

[nickytonline]

We should probably run vitest first, followed by a build and then the e2e tests.

That's not possible with the current workflow setup (it just runs npm run test), so I'll move build up.

Before you go further with Cypress @diivi, I left a comment about investigating Playwright instead. See #238 (comment)

[bdougie]