experiences with testing the backend or e2e?
Hey all,
Does someone here already have experience with testing the backend or e2e? According to the docs only frontend testing is currently supported. But I thought maybe someone has set up a custom testing infrastructure and would love to hear about it. How did you do it and can you recommend setting it up?
1 Reply
Hey @Gwaggli !
We do have some e2e tests set up, that we use to test new releases of Wasp, by running them on prepared Wasp apps to check if they are still working as theys should. @miho set those up using Playwright. You can see those here: https://github.com/wasp-lang/wasp/tree/main/waspc/headless-test . If you need any help with setting that up, ping us, we are happy to help!
As for unit/integration testing -> Wasp 0.11 has support for testing frontend, it doesn't have support for testing backend. That said, Wasp 0.12 is coming out in a matter of days (end of this week, or next week) and will open up Wasp quite a bit by introducing package.json, which should also make it much easier to run test for both frontend and backend. So I advice waiting a week for that, and giving it a try, and we can also help with that if there are any hiccups, as you will be one of the first ones to use it probably -> so you can tell us if you encounter any issues and we can work on it together.