This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-18
Channels
- # admin-announcements (3)
- # alda (1)
- # boot (85)
- # capetown (4)
- # cider (10)
- # clara (16)
- # cljsrn (3)
- # clojars (35)
- # clojure (83)
- # clojure-austin (8)
- # clojure-brasil (4)
- # clojure-canada (16)
- # clojure-greece (2)
- # clojure-ireland (7)
- # clojure-russia (23)
- # clojure-spec (22)
- # clojure-uk (151)
- # clojurescript (97)
- # core-async (10)
- # cursive (1)
- # datascript (7)
- # datomic (21)
- # defnpodcast (13)
- # devcards (3)
- # emacs (4)
- # events (3)
- # hoplon (18)
- # juxt (4)
- # leiningen (7)
- # mount (4)
- # off-topic (2)
- # om (1)
- # onyx (30)
- # planck (6)
- # proton (81)
- # re-frame (3)
- # reagent (9)
- # rum (10)
- # spacemacs (1)
- # specter (6)
- # testing (7)
- # untangled (66)
- # vim (84)
- # yada (23)
@paulspencerwilliams: My team does but I'm not that close to tests they're writing. I've used it a fair bit in the past.
@agile_geek: Cheers. I’ve resolved an issue I was receiving last week trying to convert their DataTable java objects into something a little easier to consume in Clojure.
I've got some stuff where I was using Cucumber in a Clojure project about 18 months ago. I had fun getting it to work with Kerodon (did in the end). Also submitted a PR to fix the Clojure Cucumber JVM example as it had stopped working with latest Clojure version at time.
It's got a bad rep, but it's a good tech to use when you do have non technical stakeholders in the room and need to agree what the system should do in particular situations. It's not a test tool per say though.
Agreed.
I often work with QA who can't write code and its useful for them if they have support from devs to write steps or they get some basic training to write a bit of the glue code