The book Effective Debugging by Diomidis Spinellis describes 66 different approaches for effective debugging of applications and systems. It provides methods, strategies, techniques, and tools for finding and removing faults, and gives examples for using them in different settings.
How do you handle a long list of defects in your project? You don't. If it is not worth fixing a defect right now, it’s not likely that we will find the time to do it later. Also, it becomes more and more difficult over time to correct the defect, so it is cheaper to solve it now. Kirill Klimov explains why you should solve defects right away, or state that you will not solve them.
Mike Talks, Test Manager at Datacom, gave a talk at the Agile New Zealand 2015 conference on Deprogramming the Cargo Cult of Testing. Afterwards he explained why agile testing needs deprogramming, and how this can be done.
The book Fifty Quick Ideas to Improve Your Tests provides suggestions that cross functional teams that are doing iterative delivery can use to manage and improve their testing activities.
After a flurry of activity from thier open working group Swagger 2.0 was officially released in September 2014. Since then responsibliity for leading Swagger would be handed over to SmartBear.
With desired agile team traits like self-organising, role blurring and skill diversification, do we still need Test Managers in agile? How are the activities which have long made up the role divested?
Common System and Software Testing Pitfalls provides 92 pitfalls that make testing less efficient and effective. It aims to help you to avoid falling into pitfalls or dealing with the consequences.
This article is the first article in a series on managing remote teams, which shares experiences in developing a process for remote collaboration.
We mostly ship software by date, prioritizing what we think is important, and shipping once out app passes a certain quality level. But can we tell the readiness status of our application?
"How Google Tests Software" is an informative and interesting look beneath the covers of how a large technical organization like Google deals with the complexity of software testing. 1
“Experiences of Test Automation” is a compilation of experiences in the field from a multitude of organizations and technologies, including both obstacles and achievements, successes and failures.
Rajneesh Namta shares his thoughts, experiences, and some of the critical lessons learned while implementing software test automation on a recent Agile project. 5