Agile methods have many traditional test management activities built into them. With desired agile team traits like self-organising, role blurring and skill diversification, the nature of test management is changing. We have to question whether the role of Test Manager should exist in effective agile organisations and how the activities which have long made up the role are divested?
On the occasion of Selenium's 10th Birthday Celebration, a bunch of ThoughtWorkers have compiled an anthology of essays on testing approaches, tools and culture. This anthology of essays is available as an eBook, titled - "Perspectives on Agile Software Testing".
Rajneesh Namta shares the lessons he’s learned while automating software tests on a recent Agile project. The techniques he recommends illustrate how the Agile principles we follow when building software apply equally as well to building an automated regression test suite: start small, build iteratively and incrementally, prioritize, focus on value, work transparently, respond quickly to change.
Gojko Adzic has written Specification by Example in which he provides advice and guidelines on adopting this approach as a way to create living documentation on a software development project. 7
This article shows how automating certain programmable aspects of a test suite can help software delivery. Covered are automated testing, costs per deployment, tests as documentation & manual testing. 6
More development teams are putting testing front and center, and using TDD. Lisa Crispin covers how attitude and curiosity have shaped her career and kept her passion for testing software fresh. 3
This article touches upon challenges to adopting agile methods within the enterprise and provided strategies for addressing them. 9
In this interview James Bach covers topics like: engineering, why we should be telling success stories, opening our minds to other scientific domains, automated testing and exploratory testing.
In this article, the layered architecture of test automation is presented to solve the problem of test logic getting buried in unrelated supporting code. 9