pablobm left a comment (openstreetmap/openstreetmap-website#6497)
Right, that's exactly it. The difference with controller tests is that you get
to browse across different controllers, not just the one. The difference with
integration tests is that you browse via clicking links, submitting forms, etc,
as opposed as sending low-level HTTP requests.
In general, my view is that it's best to avoid Selenium unless you really need
JS. In this case, the tests involved typically are about the profile section
and similar, which don't need JS most of the time. Anywhere we think the JS is
relevant, we can add back.
The implementation would look something like "Selenium by default, except in
these tests where we use rack-test" or the other way around.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6497#issuecomment-3481653211
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/6497/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
