2,492 reputation
611
bio website lizkeogh.com
location London, United Kingdom
age
visits member for 3 years, 10 months
seen May 12 at 9:41

London-based Lean / Agile coach and trainer, developer, haiku poet, early BDDer and international speaker.


Nov
30
comment How to be successful at BDD Specifications Workshops?
@DNA I've covered complexity estimation in more detail in this post: lizkeogh.com/2013/07/21/estimating-complexity - the ease of tracking down expertise is indeed part of the metric.
Nov
17
comment Should selenium tests be written in imperative style?
This made me smile, since the original intent of using "should" in BDD was to invite exactly this kind of question and consideration of context. True, though. :) dannorth.net/introducing-bdd
Sep
9
awarded  Yearling
Aug
16
comment Design patterns - do you use them?
(Actually, it's not just new devs - even more experienced devs overabstract sometimes. Took me a month to get Dan North's visitor pattern out of JBehave; he still tells that story!)
Aug
16
comment Design patterns - do you use them?
@Juha-Untinen If code has simply been developed without reference to patterns, it's unoptimized, but can be refactored without too much trouble. New devs tend to put too many patterns in, and those patterns can often be cemented in place. I'd recommend letting an experienced dev pair with a junior, or teaching them TDD which helps the patterns to emerge, rather than letting anyone program against known patterns or blind. And devs can experiment safely with katas, rather than production code.
Jul
21
answered When to write tests for a new class using BDD?
Jun
26
revised bdd wiki description
The whole point of BDD was to avoid the word "test". And it's not about the tools.
Jun
26
suggested suggested edit on bdd tag wiki
Jun
23
awarded  Tag Editor
Jun
23
revised bdd wiki excerpt
Added some stuff around conversations and examples.
Jun
23
comment Is BDD actually writable by non-programmers?
Ironically, JBehave 1 (the first BDD tool) started by generating business-readable scenarios. We didn't parse English until Cucumber. I think JBehave 1 was useful for actually reminding people that they had to talk about them first...
Jun
23
suggested suggested edit on bdd tag wiki excerpt
Feb
27
comment Is BDD scalable for medium to large projects?
@AlexandreMartins Hah, absolutely! Much more important to recognise that you might have poor quality tests & scenarios than to pretend they're all good IMO.
Feb
24
answered Is BDD scalable for medium to large projects?
Feb
17
comment Behavior Driven Development and Unit Testing in Python
This. From what I'm reading, Lettuce and Behave are higher-level BDD frameworks, like Cucumber, meant to capture scenarios discovered in conversation with business stakeholders. If you're just communicating with other devs, they can read code; don't worry about using a BDD tool. Any unit testing tool will do the job. I sometimes put my class-level Given, When, Then into comments.
Nov
19
comment How to be successful at BDD Specifications Workshops?
That's a good way of putting it, yes :) Also, having the conversations is more important than writing them down, which is more important than automating them.
Nov
18
answered How to be successful at BDD Specifications Workshops?
Sep
28
awarded  Guru
Sep
9
awarded  Yearling
Aug
30
comment How to edit existing user stories
Don't use Cucumber to test aesthetics. You're always going to verify them manually anyway, and check again every time they change. Just tie it to what the customer really wants, eg: "As a producer, I want to be able to see text clearly against the background", and leave the rest of it up to the UX guys. Aesthetics and usability are not good candidates for BDD scenarios IMO. The only exception to this is if you're producing some kind of GUI framework for use in another application (in which case what you have is fine).