Web tests can be run to ensure changes didn’t break something.
They can be a bit finicky so I’d suggest having web tests be a separate task than regular unit tests & the build not necessarily depend on them passing.
I don’t mind setting this up & making a pull request if there are no objections. I see we have a registration page now, so a web test can be added for that.
1 Like
Why not run them on the version-control / continuous-integration server, at least?
And why not refuse to merge an update to master if it breaks one of those existing tests?
We could do that, but as I mentioned they can be a bit finicky with timeouts & stale elements.
It won’t be noticed at first, but once we have a thousand web tests, it can be a little annoying.