Looking for suggestions for testing

[sbennett33]

Thanks for this library! I've been playing with it locally and it looks great so far.

One piece of the story I want to figure out before I suggest this to the rest of the team is testing. I know it's fairly straightforward to test the controller responses but I'm wondering what the best method is for testing the frontend and if anyone has any tips for integrating that testing into the rest of the project. Are people doing End-to-End testing with something like Wallaby or Hound? Unit testing the frontend separately using Jest/Mocha? Just saying YOLO and shipping it?

Any thoughts or suggestions would be greatly appreciated.

[derrickreimer]

Hey @sbennett33! I suspect it varies quite a bit depending on your needs and preferences.

Some thoughts:

• It should be possible to use something like Wallaby for end-to-end tests, with SSR enabled (so that there's rendered HTML content coming from the server-side to test).
  • In practice, I've found these kinds of tests to be a bit slow and brittle (this is not an Inertia-specific observation), so I typically avoid them in my own projects. But to each their own.
• You could explore something like React Testing Library for testing the page components.
  • In practice, I've not found these kinds of tests to be particularly valuable, especially if I'm (1) using TypeScript (to catch bugs related to passing around unexpected props & data), and (2) keeping the front-end as dumb as possible and doing most of the logical heavy-lifting on the server-side.