Clojurians Log v2

can you recommend projects which have such a test suite which demonstrates a good testing style?

im surprised to see that most helper libs has terrible failure output

@malcolmsparks: just looked at iota again, because it seems to be the least invasive extension to clojure.test, but im getting output such as:

FAIL in (test1) (core.clj:7)
expected: (clojure.core/= ((juxt.iota/as-test-function :a) G__3713) 123)
  actual: (not (clojure.core/= 1 123))

(deftest test1
  (given {:a 1} :a := 123))

then there is https://github.com/AvisoNovate/taxi-toolkit/issues/4 which is also about the terrible output, but no one has touched it for over a year.

i have the feeling that im trying to do things the wrong way, because i find it hard to believe that people are so ascetic that they dont care about improving it

i also tried to do such a simple thing as pressing a next button on a webpage and expecting it to modify the url (`(io.aviso.taxi-toolkit.composite-assertions/assert-nav :next-btn "/#/page2)`) and it was just timing out for quite long, while the actual issue was having 2 next buttons on the page, but the 1st one was hidden...

and im only trying these extra convenience layers because the clj-webdriver.taxi tools are even more low level, although it is supposed to be the high-level api to selenium

i havent even found good examples of how to press a button - irregardless of it's type input/a/button - just based on its label. i thought that's the recommended way of keeping integration tests user centric and resilient to UI changes, but then it turns out i need xpath expressions to achieve this!? i can't recall having such issues when i was solving similar issues with capybara-like tooling in the ruby and the nodejs worlds. what am i missing?