This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (3)
- # architecture (2)
- # beginners (54)
- # boot (85)
- # braveandtrue (8)
- # cider (21)
- # cljs-dev (56)
- # cljs-site (5)
- # cljsjs (15)
- # cljsrn (9)
- # clojars (4)
- # clojure (99)
- # clojure-austin (1)
- # clojure-russia (36)
- # clojure-spec (53)
- # clojure-uk (29)
- # clojurescript (161)
- # datomic (8)
- # hoplon (3)
- # immutant (48)
- # jobs (1)
- # jobs-rus (1)
- # leiningen (10)
- # om (23)
- # om-next (1)
- # onyx (22)
- # parinfer (3)
- # planck (13)
- # protorepl (8)
- # re-frame (46)
- # reagent (2)
- # remote-jobs (1)
- # respo (1)
- # specter (5)
- # testing (12)
- # untangled (50)
- # yada (13)
I'm not sure if it's the relief of only having to put up with one of most frustrating jobs I've ever done for another week or the fear that I won't get a contract after this one but my writers block from the weekend has gone and I'm hammering out my latest blog.
This blog is going to be mammoth (or possible Mastodon @otfrom?). I'm only approx half way thru and this is just part one of a series of brain dumps on how I do design. Needs heavy editing after I've got it down. I may be taking my laptop on Holiday with me to finish it. No Clojure in it though 😦
Someone pick a Clojure subject of the day please.
guy: Glib answer: Do some! More expansively, what specifically do you want to discuss?
testing frameworks in clojure and which ones are good. I’ve always used quite an old library with clojure.test but am looking for something new.
Sure. I had a bit of a flirtation with Midje for a while as I liked the readability of it. However, it's very heavily dependent on macro's that don't compose well and if you use REPL based tooling and things like CIDER Midje is not well supported.
I want to look at Expectations but when I briefly looked at it over a year ago again the tooling support let it down.
I use test.check for property based (generative) testing but I find that supplementary to example based testing. If you're interested I wrote a couple of blogs on it at the beginning of the year.
Over to others for their favourites!
I like speclj and expectations, my preferred style involves an
autotest runner that runs tests on file change, and integrates with growl.
@agile_geek: sure whats the link?
@glenjamin: dumb question, have you tried using speclj with https://github.com/stuartsierra/component ?
@guy: https://chrishowejones.wordpress.com/2016/04/04/prop-up-your-tests-with-test-check/ for part 1 and https://chrishowejones.wordpress.com/2016/04/11/what-state-are-your-properties-in/ for part 2
that reminds me, this is that blog post i mentioned last week @agile_geek http://blog.glenjamin.co.uk/names-values-identities-states-and-time
@glenjamin: I like the river analogy 'flowing' through that blog. Cool (and no doubt refreshing!)
a = 1 f(a); // a is 1 b = “123” g(b); // b is “123” c = [4, 5, 6] h(c); // c could be anything
Yep. The defining characteristic of Clojure for me is that state changes become explicit.
The most annoying characteristic is that lazy vs strict evaluation isn't!