You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that SSR is possible with Inertia.js, it opens up some really interesting possibilities when it comes to testing an Inertia app. It now seems possible to have the tests actually generate the page HTML. This would allow us to check for any errors when rendering the page, and also run HTML ("see") assertions against the rendered HTML.
I'm creating this issue as a reminder to test this out when I have time. 👍
Something to explore: Automatically removing the data-page attribute in testing mode, so that when you run an HTML assertion, it doesn’t match against the JSON encoded page object, but has to match against the actual rendered HTML. For example:
@reinink Hi there and thank you so much for your work with this package, Jonathan! 💪 😎 🚀
I've only just started (this week) with wrapping my head around the architecture and architecture possibilities with SSR/Inertia. So please excuse my n00bness.
Otherwise, I just wanted to mention that your config idea here - is awesome and ideal (as you already know lol).
Additionally, re: your second idea here - is also super interesting and if I'm picking up what you're putting down... just spitballing here... but in theory couldn't we actually do a proper automated html validation check test with functionality like that - essentially pushing the node rendered markup back into either PHP/JS' hands for a w3c-based valid html/css check script to run on that returned markup?
If so, both of these would be insanely awesome additions to your already impressive functionalities, so if there's any way I can help, please let me know!
PS - there may very well already be ways to automate HTML validity checks via Laravel/PHP that I'm unaware of, as well. But I quite like the idea of working with a stack that let's me use PHP or Laravel or even JS to automate such tasks. That flexibility would open up lots of opportunities from a full-stack web design system POV, you know?
Now that SSR is possible with Inertia.js, it opens up some really interesting possibilities when it comes to testing an Inertia app. It now seems possible to have the tests actually generate the page HTML. This would allow us to check for any errors when rendering the page, and also run HTML ("see") assertions against the rendered HTML.
I'm creating this issue as a reminder to test this out when I have time. 👍
Possible new config:
Something to explore: Automatically removing the data-page attribute in testing mode, so that when you run an HTML assertion, it doesn’t match against the JSON encoded page object, but has to match against the actual rendered HTML. For example:
The text was updated successfully, but these errors were encountered: