This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # beginners (1)
- # boot (37)
- # cbus (1)
- # cider (44)
- # cljs-dev (16)
- # cljsjs (2)
- # cljsrn (18)
- # clojure (205)
- # clojure-belgium (6)
- # clojure-china (1)
- # clojure-india (1)
- # clojure-russia (24)
- # clojure-spec (21)
- # clojure-turkiye (1)
- # clojure-uk (72)
- # clojurescript (91)
- # core-async (4)
- # cursive (12)
- # data-science (2)
- # datascript (2)
- # datomic (12)
- # emacs (6)
- # flambo (7)
- # funcool (12)
- # hoplon (24)
- # incanter (2)
- # jobs-discuss (29)
- # keechma (2)
- # lein-figwheel (2)
- # leiningen (2)
- # mount (13)
- # nyc (2)
- # om (76)
- # om-next (1)
- # onyx (38)
- # other-languages (4)
- # planck (40)
- # re-frame (33)
- # reagent (101)
- # ring-swagger (5)
- # slack-help (1)
- # untangled (7)
- # yada (14)
I haven't used expectations but it looks promising especially the better error messages. Also it looked we easier to read, and as I feel automated tests are one of the more reliable forms of documentation, that's important.
I've blogged about test.check and stateful-check and I can see both being very useful for generative (property based) tests. However, like all tests, they need investment of time and thought. I feel that investment pays off in better understanding of the problem and support when making inevitable changes.
Testing, like clean coding, is completely misunderstood by most managers (and even more lamentably lots of devs). They don't realise that investment in the right techniques applied at the right level leads to faster progress in anything except the smallest throw away prototype (and even then I add tests as over half the prototypes I've been involved with shipped)
I've seen a lot of contradictory studies around the impact of tests, particularly TDD. There's nothing definitive but there's evidence that tests speed up, slowdown and have no impact on development times, depending on the study, and in one I read I saw all 3 in sane study.
However, there is better evidence that they reduce bug density in production.
I've not seen anything that talks about whether systems constructed using tests as a guide (whether it's test first, TDD or even test after but before change) are easier/faster/cheaper to change. I'd like to see studies on that.
Anecdotally I've experienced automated testing support faster refactoring to introduce new requirements late in a project without edit and pray syndrome. Also I've onboarded new developers with little support by simply piloting them to the tests.
Phew... That's a lot of brain dump for this early in morning!
all automated checking help prevent mistakes
@yogidevbear: i've used midje quite a lot in the past, and spent quite a lot of time fighting its dsl and finding weird macro edge cases. currently i'm just using clojure.test
I'm still a newbie when it comes to testing. But I think that until you are in a situation where you realize tests are making your life much easier (not just the small demo that shows how to do testing/tdd/whatever test flavour) it's hard to get it right
IME the biggest advantage of good automated tests is verifying that behaviour isn’t regressed unintentionally when making an unrelated change
and making an unrelated change and worrying about regression pretty much never happens in a university setting
I've yet to come across anybody who have used Midje and still likes it.
I've used Midje a fair bit but all my projects are 'toy'. I don't dislike it but I've migrated back to clojure.test and I can't put my finger on why exactly. I think tool support and lowest common denominator are probably the factors. However, I think clojure.test is the least readable IMHO.
i really like having autotest+growl, and then I treat “save” as my “run all tests” button
autotest in CIDER is quite nice.
I was comparing notes with colleague recently, who doesn’t like that approach, and we think it might be because she’s used to saving continuously - even when stuff doesn’t work
Last time I tried Expressions I found the expression mode in emacs didn't seem to work. Not sure if that's been fixed.
One of the things I like about using “save” as the trigger is that you can easily trigger lots of tools off the same action, and it’s editor agnostic 🙂
I liked it at the start for testing small pure functions but in a big project I just ended up spending all day trying to get its strange macro do do what I want
And it has loads of features that seem to overlap and the docs don’t really tell you which ones you should actually use
Expectations is my favourite but I often end up using clojure.test because of tooling support and it’s easier to use with test.check
is anyone using this? https://shaunlebron.github.io/parinfer/
Drinks in Camden tonight if anyone is around.
@malcolmsparks: 300 miles away otherwise you wouldn't be able to stop me!
@agile_geek: how do you do it?
@malcolmsparks: what travel every week? Got to admit I'm getting tired of it but I get lots of learning done on train! This week I travelled home on Wed and I was at Sunderland Uni yesterday so WFH today.
@quentin: parinfer is really cool. one trick to know is that indenting matters. but once you know that it works really well
@malcolmsparks: I am only 60 odd miles away… but still can’t make it 😞
@benedek: obviously. Don't you just live Windows...just remember..don't click on any red crosses!
But surely Microsoft aren't forcing you to upgrade! You can undo your misintended red cross click by simply modifying the registry...
haha, tbh i wrote this nice little script and gave a try to
inlein which i really liked. the only tight spot was making it run on my colleague’s win machine
Unfortunately I have to work on Windows 7 machine locked down so I can't install anything, can't connect to public wifi, access internet through a firewall that won't let me browse github or read 90% of the technical blogs I need to reference.... Now you know why I bring my own laptop in with me and connect that to public wifi otherwise I would not be able to communicate with you good people. 😉
sounds like some financial institution @agile_geek 😉
yeah indeed. use this pretty awesome browser stack service when have to test something on IE now and then
@agile_geek: does the company in case really think it is adding value doing things that way?
@benedek: they have an odd perception of risk. Lock everything down so that every developer wastes at least 4 weeks of the year raising tickets to install and unlock stuff ✅
Spin up 50 teams where one would do, write millions of lines of untested code that is unstructured and contains massive duplication ✅
@agile_geek: I hope they pay you really well for that? 💰
@agile_geek: if the company in question spins up 50 teams, surely a (range 1 5) man team can deliver the same functionality in less time with some Clojure?
@thomas: same company could deliver same functionality in existing lang (Java) with 10 teams! Less is more! Could do it in Clojure with 3-4!
Mind it would help if 90% of developers knew what SRP was or even what delegation is!
Actually had to explain what a method was to one of them!
@malcolmsparks: when/where in camden?