Fork me on GitHub
#clojure-uk
<
2017-05-10
>
jonpither09:05:29

Hope you landed safely @seancorfield

korny09:05:37

Hmm - just saw the cucumber stuff. We used it heavily at my last job, around 2008ish, and frankly it sucked - we never really got it refactored into a clean DSL, you were always fighting it. These days most people I work with use BDD language but in a normal test tool like junit or spock

korny09:05:29

I really like Spock if you are doing Java-world testing, you can use BDD language, you can do tabular tests, you can initialise data using groovy rather than Java pain.

agile_geek09:05:23

I have mixed experiences with Cucumber but most of the pain in BDD testing has come from driving the UI using it. I prefer making the rendering layer as thin as possible and using BDD to drive most of the e2e tests against an API just below (inside?) the rendering layer with a few 'smoke' tests on the full UI on critical use cases (e.g. shopping bag, payment journey, etc).

agile_geek09:05:54

@seancorfield ditto hope the journey was OK...or as OK as it can be given the circumstances.

seancorfield10:05:30

Thanks. Yeah, day at mum's. Then down to Devon tomorrow.

mccraigmccraig13:05:28

anyone had any bad experiences with loading yourkit agent on production vms ?

jonpither14:05:06

do you prefer yourkit over visualvm?

mccraigmccraig14:05:03

don't know @jonpither - i've used yourkit to debug many memory issues in the past and am familiar with it, not so much visualvm

jonpither14:05:21

jvisualvm just works with jmx ports I think, so no need for the agent

jonpither14:05:33

but haven't tried yourkit as an agent in prod

mccraigmccraig14:05:14

i think you can use yourkit without the agent too, but with restricted capabilities

dominicm18:05:52

you have to hook up jstatsd to use visualvm on a remote system with more than restricted capabilities

mccraigmccraig18:05:48

yourkit is doing great - more expensive than visualvm tho