~~It would be nice to pass HTML into `Pages.click` instead of just the page~~ `Pages.click` should ideally help you figure out why a selector didn't find anything to click on (especially in a very large page)

[eahanson]

[sax]

This might be challenging, since we need state from the driver in order to actually be able to interact with the page. Or rather... if we click on the html without the page, we can't actually do anything. Any click from a controller test needs the conn as well as the html. Any click from a live view test needs the live view and does not actually need the html.

[eahanson]

The tension here is that the failure message is hard to understand when the selector doesn't find anything. I'll update the title

[eahanson]

For example, if your selector was "#foo table tr[test-role=some-row]", and no matching nodes were found, it could tell you things like "found '#foo table' but it had no 'tr' elements" or "did not find #foo"