By working together to create the set of tests and then determining where that testing belongs, we can increase efficiency, reliability and reduce debugging time for failures in the future.
Many organizations are adopting Agile development practices and the Scrum framework for project management. With a software testing perspective, one of the main challenges of this approach is to complete all software testing activities during iterations that could last only one to two weeks. In this article, Clemens Reijnen provides five tips for getting software testing done in a Scrum sprint.
In this blog post, Jonathan Kohl discusses the similarities between software testing and game playing. He defines a game as a “situation involving cooperation and conflict with different different actors with different motivations and goals”. He sees software testing as an individual pursuit within a larger software development game and with two styles: scripted testing and exploratory testing..
Many software development projects struggle with creating and communicating a software testing culture that is appropriate for their needs, which might decrease software quality by leaving bugs undiscovered. Previous research suggests that social coding sites such as GitHub provide a collaborative environment with a high degree of social transparency. This makes developers’ actions and interactions more visible and trackable.
What’s the effect of exploratory software testing on a Team? What effect the practice has on their leader? Shmuel Gershon team experience in user centered Context-Driven projects made them realize that more than technical practice, it calls for change in leadership style and interactions.
This video describes the six mechanisms in Visual Studio 2010 that enable more effective collaboration between developers and testers. These mechanisms include tools to create actionable bugs, debug historical events, and automate functional testing. Effective collaboration between developers and testers is paramount and can make the difference between shipping quality applications on time, or slipping because bugs are found late.
This post discusses about the fact that software testers don’t have responsibility for software quality any more than anyone else in the development team. Everyone has that responsibility.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates