Posts Tagged BDD
Scenario-Oriented vs. Rules-Oriented Acceptance Criteria
Posted by AntonyMarcano in Agile, BDD/ATDD, Business Analysis, Software Development, Software Testing, Uncategorized on October 2, 2011
Acceptance Criteria, Scenarios, Acceptance Tests are, in my experience, often a source of confusion. Such confusion results in questions like the one asked of Rachel Davies recently, i.e. “When to write story tests” (sometimes also known as “Acceptance Tests” or in BDD parlance “Scenarios”). In her answer, Rachel highlighted that: “…acceptance criteria and example scenarios [...]
Old Favourite – More Sharks and Delaying Critical Mass
Posted by AntonyMarcano in Agile, Business, Business Analysis, Old Favourites, Project Management, Software Development, Software Testing on June 7, 2011
This article originally featured on my old blog on 19th January 2010. In a previous post I talked about Critical Mass of software. I showed how an ever-increasing cost of change resulted in it becoming more economical to completely rewrite the system than to enhance and maintain the original. I explained how this could be [...]
Old Favourite – Sharks, Debts, Critical Mass and other reasons to Sustain Quality
Posted by AntonyMarcano in Agile, BDD/ATDD, Business, Business Analysis, Old Favourites, Project Management, Software Development, Software Testing on June 7, 2011
This article originally featured on my old blog on 18th January 2010. A while back I tweeted about critical mass of software: Critical Mass of Code – past which the changeability of the code is infeasible, requiring that it be completely rewritten. An elaboration of this might be: Critical Mass of Software: the state of [...]
Cucumber – with step-free access
Posted by AntonyMarcano in Agile, BDD/ATDD, Software Development, Software Testing on May 29, 2011
A while back I wrote about writing feature specs (acceptance tests) at the right level of abstraction. I explained how we want to pitch our scenarios at the “task” level… Goal: What we’re trying to achieve which has one or more… Tasks: The high-level work-item that we complete to fulfil the goal, each having one [...]
Putting Cucumber where it’s not supposed to go will hurt!
Posted by AntonyMarcano in Agile, BDD/ATDD, Software Development, Software Testing on March 7, 2011
Today, I came across this post by Ryan Bigg where he talks of the pains he’s experienced with Cucumber. Fortunately for Ryan, the outcome was a positive one, he ended up finding what appears to be a nice looking API for automating test-execution. The experience he had with Cucumber, however, is a common one. Often [...]
A bit of UCD for BDD & ATDD: Goals -> Tasks -> Actions
Posted by AntonyMarcano in Agile, BDD/ATDD, Business Analysis, Software Development, Software Testing on March 6, 2011
There’s something wrong with many behaviour specs (or acceptance tests). It’s been this way for some time. I’ve written about this once or twice before, referencing this post by Kevin Lawrence from 2007. So, first things first, I want to take this opportunity to update the terminology I use… Goals -> Tasks -> Actions A [...]
You’re almost cuking it…
Posted by AntonyMarcano in Agile, BDD/ATDD, Business Analysis, Software Development, Software Testing on August 25, 2010
In “You’re Cuking it Wrong”, Jonas Nicklas, shows several examples of bad scenarios (or acceptance tests whichever term you prefer) and demonstrates better approaches. This is an excellent post on common mistakes made when writing example scenarios with Cucumber. I think, however, he could have gone further in one case. One of his examples of [...]
Being a youDevise Developer – Week 1
Posted by AntonyMarcano in Uncategorized on July 18, 2010
In my previous post, I gave the background to me spending the next month or two as a developer on a youDevise product. I’ve just completed my first ‘official’ week working with them. It was one of, if not, the smoothest of inductions I’ve ever experienced. I arrived and was shown a desk to work [...]
About
Antony Marcano is a consultant in software craftsmanship, effective software processes, software quality and software testing. He has over fifteen years experience with... (read more)
