Things Testers Miss


Bugs slip into production in spite of the best efforts of designers, coders, and testers. While testers may not be responsible for the introduction of bugs to the system, they bear some responsibility for the introduction of bugs to the user. Testing can be adjusted to reduce the number of bugs that pass through to production--without necessarily requiring more resource.


About the author

James Lyndsay's picture James Lyndsay

James Lyndsay is an independent Test Strategist, based in London. He's spent well over ten years in software testing, and has been the principal consultant at Workroom Productions since its formation in 1994. As a consultant, he's worked in a variety of businesses and project styles; from retail to telecommunications, from rapidly-evolving internet start-ups to more traditional large-scale enterprise. He's worked to technical requirements for companies that make and sell software, to commercial requirements for companies that buy and use software, and to unexpected requirements everywhere. Aside from consulting work, James works with to independently evaluate test tools, runs a mentoring scheme for test managers, and continues to be an internal irritant to ISEB/ISTQB. James is becoming a regular speaker at international test conferences, delivering keynote talks at STAREAST and AsiaSTAR in 2003. He received "Best Paper" at STARWEST 2002 and at EuroSTAR 2002 for Adventures in Session-Based Testing. See for more details. James is also a director of The Manual, a not-for-profit organization whose aim is to gather and publish basic skills.

StickyMinds is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, is the place to go for what is happening in software development and delivery.  Join the conversation now!