Lunivore

2,290 reputation

510

bio	website	lizkeogh.com
	location	London, United Kingdom
	age
visits	member for	2 years, 9 months
	seen	Jun 8 at 10:32
stats	profile views	240

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

	2,290 reputation	bio	website	lizkeogh.com	visits	member for	2 years, 9 months
510 badges		location	London, United Kingdom		seen	Jun 8 at 10:32

summary answers questions tags badges favorites bounties reputation activity

118 Actions

suggestions reviews revisions comments badges posts accepts all

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).
Aug 20	comment	Is 100% code coverage a pipe dream? I've worked on a project which had 100% coverage, so, it's possible. However, we didn't ship (coding the wrong thing), and in retrospect, having the time to reach 100% coverage should have been a red flag...
Aug 20	comment	Is 100% code coverage a pipe dream? The question is tagged "TDD". TDD is more a design tool and a problem exploration tool than a testing one, and each "test" is just an example of how the code will behave in some context, so that people can read and understand what's going on, then change it safely. TDD done well tends to lead to cleaner, easier-to-use code, and running the tests just checks that the documentation is current. Most TDD suites hardly ever catch bugs; it's not what they're there for. I think you're being downvoted because your answer betrays that lack of understanding, and I hope this comment helps with that.
Aug 12	comment	BDD in .NET - Chicken or Egg or..? @guillaume31 Hopefully you've got the features and behaviours down in steps 1, 2 and 3. 4 says "don't worry about automating against the UI". So the only ones which actually touch the UI are 5 and 6. At some point you do need to touch the UI, but I think spending 2/3 of the steps steering people away from that is fair. You may be right, though; even spending 1/3 of the steps worrying about the UI is probably too many.
Aug 10	answered	BDD in .NET - Chicken or Egg or..?
Jun 14	answered	Is BDD actually writable by non-programmers?
May 30	comment	How abstract should you get with BDD Or Exploration, for that matter. Exploration by example works very well for me.
May 30	comment	How abstract should you get with BDD @Pangea I don't like the word Specification either, just because it makes people try to define their scenarios with certainty for the entire feature, instead of accepting that there will always be some uncertainty in anything new, then exploring that and trying something out to get feedback. Recognizing uncertainty is IMO far more important than eliminating it. It's just examples, conversations, desires, hopes - not specifications. But yes, if you can keep that in mind, read Specification by Example. Just replace the word Specification with Conversation and you'll be good.
May 30	answered	How abstract should you get with BDD
May 30	comment	Wisdom of using open source code in a commercial software product +1 for licensing issues. Check carefully that using some open-source component won't force you to open-source your own code too. I don't believe this will be the case for most open-source, and if you're just using it to produce or host your code there will be more available, but worth checking nonetheless.
May 8	answered	How to set up a one-man research in the difference between BDD and Waterfall?
Apr 5	comment	“// …” comments at end of code block after } - good or bad? @trinithis Sorry, I can't work out what you mean when it's all on one line like that. I think I mentioned that there are also other ways of refactoring code that devs doing this could learn.
Apr 5	comment	“// …” comments at end of code block after } - good or bad? @trinithis It's not about whether it's bad or not, it's about effective ways to help people get better so they grow through it. Being effective > being right. It's also a perfectly sensible thing to do if, say, you're refactoring legacy code that's even more of a mess. Sometimes bad things can make better interim steps and lead to something even better than that.