Agile testing tutorials and how to content : Test-Driven Development (TDD), Behavior-Driven Development (BDD) and other agile approaches for software testing.
In this short article, Mahfoud Amiour introduces the PURIFF acronym as a reminder to all the software testing to be conducted during the Scrum sprint. In PURIFF, P stands for performance testing, U covers unit testing, R deals with non-regression tests, I represents integration testing, F is for functional tests and the last F covers non-functional tests. A Scrum team can use it as a checklist to determine which categories of tests are relevant in the given context.
Software testing is a major activity in any software development project and a large part of the budget is spent on it. If we want to effectively spend your money, the ease of software testing should be addressed when you design your system in the early stages of building your applications. In this article, Gil Zilberfeld explains that thee adoption of test first practices like Test-Driven Development (TDD) or Acceptance Test-Driven Development (ATDD) by the majority of agile teams shows how test automation needs are addressed from the initial steps of system concepts. As an additional benefit, it is easier to evolve a testable system because you can add features knowing that existing ones did not break.
Many teams have tried to implement agile software development practices and failed. When you read about transitioning to agile development, it sounds so easy. Why don’t all of them succeed and why do so many agile adoptions go so badly? In particular, testing seems to get off track.
This article discusses the traditional software testing aspects that should be changed before adopting Agile practices. Testing teams face a significant impediment when they have to unlearn the traditional practices.
This video provides a retrospective of what went right and, more importantly, what went wrong for the software testing activity during a transition to agile.. If agile is in your future, come discover what you’re in for, traps to avoid, and how to be successful. If you’re not ready for agile, you’ll learn some new approaches that can be applied to traditional processes.
in this blog post, Lisa Crispin proposes a short explanation on how to use and interpret the Agile Testing Quadrants defined by Brian Marick. The quadrants are a taxonomy that can help teams to plan their testing and to make sure they have all the resources they need to accomplish it.
In this blog post, Dave Rooney explains that microtests and TDD are excellent practices but you still need other levels of tests and testing to sustain a team’s ability to be agile over any extended period of time.
