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

    by Ben Linders on  Jun 23, 2015

    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

    by Mike Amundsen on  Jun 09, 2015

    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

    by Ben Linders on  May 11, 2015

    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

Posted by Ben Linders on  Oct 28, 2014

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.

Working Together, Sitting Apart

Posted by Hugo Messer on  Oct 05, 2014

This article is the first article in a series on managing remote teams, which shares experiences in developing a process for remote collaboration.

Is Your Application Ready?

Posted by Gil Zilberfeld on  Nov 22, 2013

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?

Interview and Book Review: How Google Tests Software

Posted by Craig Smith on  Sep 11, 2012

"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

Book Review: Experiences of Test Automation

Posted by Manuel Pais on  Apr 27, 2012

“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.

Thoughts on Test Automation in Agile

Posted by Rajneesh Namta on  Feb 21, 2012

Rajneesh Namta shares his thoughts, experiences, and some of the critical lessons learned while implementing software test automation on a recent Agile project. 5

Virtual Panel: Specification by Example, Executable Specifications, Scenarios and Feature Injection

Posted by Jon Arild Tørresdal on  Nov 10, 2011

InfoQ have talked to Dan North, Gojko Adzic, Elizabeth Keogh and Matt Wynne about Specification by Example, Executable Specifications and Feature Injection and how they relate to BDD. 1

Introducing the Tellurium Automated Testing Framework

Posted by Jian Fang on  Sep 21, 2010

Jian Fang describes the The Tellurium Automated Testing Framework he created which uses a novel approach to try and improved the robustness of automated testing scripts for web applications. 11

A Tester's Learning Journey

Posted by Lisa Crispin on  Jun 24, 2010

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

General Feedback
Marketing and all content copyright © 2006-2015 C4Media Inc. hosted at Contegix, the best ISP we've ever worked with.
Privacy policy