BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Software Testing Content on InfoQ

  • Hit or Miss: Reusing Selenium Scripts in Random Testing

    Just like during test execution process using an ‘exploratory’ technique, which is guided by a great deal of solid analytical thinking and a good portion of randomness, we can reuse or automate scripts to achieve similar results. All you need is a well-designed test automation solution and a bit of patience. Read the article to learn how you can use this approach in your testing activities.

  • Q&A with Diomidis Spinellis on Effective Debugging

    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.

  • Now or Never: the Ultimate Strategy for Handling Defects

    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.

  • Q&A With Mike Talks on Why Agile Testing Needs Deprogramming

    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.

  • Q&A on Fifty Quick Ideas to Improve Your Tests

    An interview with Gojko Adzic, David Evans and Tom Roden on why they wrote this book, how quantifying quality can support testing, balancing trust levels when testing large and complex systems, why automating manual tests is almost always a bad idea, on using production metrics in testing, how to reduce or prevent duplication in test code, and on upcoming books in the fifty quick ideas series.

  • APIs with Swagger : An Interview with Reverb’s Tony Tam

    After a flurry of activity from thier open working group, Swagger 2.0 was officially released in September 2014. Our interview took place in March 2015, less than one year from the start of the 2.0 process and right after Reverb announced that the responsibliity for leading the future of the Swagger specification would be handed over to SmartBear, the Massachusetts-based software tools company.

  • How Agile Has Changed Test Management

    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?

  • Q&A about the book Common System and Software Testing Pitfalls

    The book Common System and Software Testing Pitfalls by Donald Firesmith provides descriptions of 92 pitfalls that make testing less efficient and effective. The descriptions explain what testers and stakeholders can do to avoid falling into the pitfalls and how to deal with the consequences when they have fallen into them.

  • Working Together, Sitting Apart

    There are essentially two factors that determine whether your offshoring adventure is successful or not – people and process. This article is the first article in a series on managing remote teams, sharing experiences in developing a process for remote collaboration. As people sit apart in (several) remote locations, extra attention must be paid to articulating how people work together.

  • Is Your Application Ready?

    We mostly ship software by date, squeezing all development and testing efforts toward that deadline. We prioritize what we think is important, and once our application passes a certain quality level, we’re ready to go live. But even when we do ship, can we tell the readiness status of our application?

  • Interview and Book Review: How Google Tests Software

    "How Google Tests Software" by James Whittaker, Jason Arbon and Jeff Carollo is a book that details exactly what is described on the cover. It is an informative and interesting look beneath the covers of how a large technical organization like Google deals with the complexity of software testing.

  • Book Review: Experiences of Test Automation

    “Experiences of Test Automation” is a compilation of experiences in the field that is hard to read from end to end but serves well as a reference for experienced readers by providing examples of approaches, obstacles and solutions in a variety of domains and technologies as well as insightful overviews from the authors.

BT