Add E2E/integration tests for critical user flows

[stanleypliu]

Thoughts on adding E2E tests (Cypress etc) to test critical user flows like logging in/signup, creating a project, locking and accessing a task and so on? I notice there aren't any at the moment. I don't think it would impact deployment times that much either.

[linear]

TECH-863

[spwoodcock]

Would love this a lot!

We have used Playwright for Field-TM and it works very well, but a bit of a pain to maintain when the project is easily stages and changing a lot quickly.

Would be keen to add Playwright here, but I think first integration tests using Vitest (per page) and PyTest (per endpoint call) would be more valuable 😄

[stanleypliu]

Yeah I was wondering whether this project is rapidly changing or just in maintenance mode, it seems to me like new features aren't being added that quickly

[spwoodcock]

We have a contract ongoing with a huge refactor to the photo upload process currently.

But mostly until Feb we are basically just struggling along with my limited time and any volunteer contribution where possible 🙏

In Feb a new lead dev starts and development will increase rapidly - lots of demand and loads to do 😁

[spwoodcock]

Consider the current state as a v1 prototype that had good success.

From here we need to significantly improve to scale with demand and make the platform as good as it can be =)

[stanleypliu]

Would love this a lot!

We have used Playwright for Field-TM and it works very well, but a bit of a pain to maintain when the project is easily stages and changing a lot quickly.

Would be keen to add Playwright here, but I think first integration tests using Vitest (per page) and PyTest (per endpoint call) would be more valuable 😄

Vitest isn't as good at testing browser-based interactions as Cypress or Playwright as you mentioned, it's more useful for unit testing IMO. What do you think about just covering the basic, critical flows with Playwright like logging in and accessing the core pages?
With regards to PyTest I can set up smoke tests for endpoints 👍

[spwoodcock]

Sounds like a good plan!

Two key criteria:

• Test quality is more important than quantity - the key workflows for users.
• The tests shouldn't add extra developer burden ideally, having to fix them regularly etc - hopefully quite resilient tests to non-breaking changes.