@thedavidmeister would you be willing to rework the tests in another PR?

I personally dont use tests yet but I thinkt the cljs direction would be faster?

sooo much better

i would be happy to put up a PR that moves the selenium tests to cljs equivalents

- all the web driver wrappers i know about for clojure are essentially unmaintained

- selenium seems to inevitably come with "random" bugs that cause builds to fail quite often when you have 1k+ assertions

- cljs tests are at least one or two OOM faster because there's no need to setup a web server and render entire pages to test one tiny element in the DOM

- it's much easier to write tests that make assertions directly against DOM elements generated by hoplon than trying to scrape the DOM (e.g. what if a previous test mutated the element that you want to inspect?)

- selenium commonly breaks when a new version of chrome/firefox comes out, not because your code is broken but because web driver needs an update to its interface with the browser version you want to use

...

i'll just put up a tx now

@flyboarder https://github.com/hoplon/hoplon/issues/174 is a perfect example of something you might want to spend 10-15 mins writing some simple tests for if you had cljs tests in place 🙂

Yep!