This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-03-27
Channels
- # admin-announcements (1)
- # aleph (3)
- # beginners (72)
- # boot (67)
- # braveandtrue (1)
- # cider (17)
- # cljs-dev (8)
- # cljsfiddle (2)
- # cljsjs (1)
- # cljsrn (2)
- # clojure (19)
- # clojure-greece (1)
- # clojure-russia (42)
- # clojurescript (15)
- # core-logic (10)
- # cursive (6)
- # datomic (2)
- # hoplon (349)
- # kosmos (3)
- # lein-figwheel (3)
- # om (52)
- # onyx (3)
- # overtone (1)
- # parinfer (11)
- # proton (11)
- # protorepl (3)
- # reagent (29)
- # ring-swagger (2)
- # spacemacs (1)
- # testing (3)
- # uncomplicate (1)
I’m not sure this is exactly a testing topic. I recently started using https://github.com/jonase/eastwood on some of my code. I was very impressed. It did find some real issues (mostly in tests, those tests weren’t doing what I intended). So: eastwood awesome! My trouble comes from a bunch of issues that eastwood found, but aren’t really in my code. It turns out that eastwood and https://github.com/scgilardi/slingshot (which I use) don’t play well together.
This https://github.com/scgilardi/slingshot/pull/55 does fix the problem, but it remains un-merged (and, therefore, unreleased).
I’d like to be able to run eastwood on Travis and fail my build if eastwood finds any issues. But, since I use slingshot’s (try+ …)
, eastwood always finds things to complain about.