Agile testing tutorials and how to content : Test-Driven Development (TDD), Behavior-Driven Development (BDD) and other agile approaches for software testing.
Test-Driven Development (TDD) has been tattered, torn, twisted, stood on its head, and pounded into an pulp of techno-fetishism. TDD was a game-changer, but the focus in the interceding years has shifted from technique to tools and TDD has been devolving into a lost art.
The increasing adoption of Agile project management frameworks like Scrum and short iteration schedule has a deep impact on the place of software testing and the activity of QA people. In this blog post, Chris Burns tries to answer the often-asked question: “what does QA do on the first day of a Scrum sprint?”
In theory everyone on an Agile team is responsible for software testing, but in practice this is rarely the case. Learn how to make quality a team sport in Scrum teams.
Behavior Driven Development (BDD) is an software development technique that use a specific format that allows both to describe the system requirements, the features, and to feed an functional software testing tool that will allow to verify the software product. In this blog post, Shashikant Jagtap explains how to write better feature files.
Software testing during the transition to Agile is not easy. This fourth and final part proposes 7 practical tips for a smooth adoption of Agile software testing practices. From better communication to test automation, these tips should help to solve some of the issues that are naturally associated with this transition. Remember that it is up to you, as a team, to implement your kind of Agile and if you love it or hate it.
It is often said that “it’s always the baker’s children who have no bread”. In this very interesting article, Ed Glas explains how Microsoft manage the load testing efforts for its Visual Studio Online tool based on a Cloud architecture.
Agile testing and test automation are almost mandatory for projects that demand high quality as well as short release cycles like Scrum. It acts as a safety net in order to protect existing functionality against bugs resulting from unintended side-effects of recent changes. Software developers “in the trenches” often automate their tests but don’t practice strict Test-Driven Development (TDD).
Copyright © 2009-2025 Software Testing Magazine by Martinig & Associates