Does ATDD really save you time?
TL DR;
ATDD + TDD significantly improve code quality and reduce maintenance costs,
and also contribute to faster project delivery and thus reduced project costs.
The article cites 2 studies:
- teams using agile development practices including in particular ATDD and TDD delivered projects 31% faster with 4 times fewer defects
- TDD significant improves the quality of the code (in terms of the defect rate)
There is always a cost involved in learning something new… and the gains might take some time to cristalize!
Acceptance Test Driven Development (ATDD) is a very effective development practice that essentially involves writing specifications in the form of documented and automated examples. These automated examples become automated acceptance tests that validate the features being delivered. The process of writing these examples encourages teams to focus on where the business value of a feature is coming from, which in turn helps developers aim for the most appropriate solutions in business terms.
Nice!
code written using good TDD practices is significantly easier to understand and maintain.
Same experience here
Full article by John Ferguson Smart
http://weblogs.java.net/blog/johnsmart/archive/2012/09/12/does-atdd-really-save-you-time
The Biggest Benefits of Test-Driven Development
Manual Testing is Unsustainable
Best bits from the article by James Grenning
Every iteration, not only does the new functionality have to be tested, but the prior iterations’ working features have to be retested too. No problem, just add some more resources; I mean plug compatible testing units; I mean people with the needed skills and knowledge.
Full article from James Grenning
Manual Test is Unsustainable
http://www.renaissancesoftware.net/blog/archives/206
Great webcast with @donmcgreal about Testing
Don steps through Unit-Testing, TDD and BDD to help us write maintainable high-quality code.
Who doesn’t want that?
Questions to consider:
- Should you test private methods?
- Should you test every getter/setter?
- What changes when you call your tests, “behaviours”?
Find the recording and many more on the Scrum.org webcast website
Adopting Test-First Development with Don McGreal
http://www.scrum.org/webcast
CopyCat is born.
CopyCat checks if your text is original and detects duplicates!
http://copycat.apphb.com/
CopyCat is a private pet project of mine, that I started to develop one month ago.
I always wanted to use all those nice shiny toys and techniques like: AppHarbour, Git, Continuous Deployment, NoSQL databases, MVC3, Cassette … and TDD, BDD approach on a green field…
So I started my own project with all those!
Bigger blog post on my blog coming soon…
RSS feed