How to Squeeze the Most Out of Your Automated Testing

Jonathan Lindo describes examples of automated test infrastructure utilizing both open source and traditional, independent-software-vendor-sourced software. In addition, he discusses new techniques for extending the value of automated testing by transforming the process from defect finding to defect resolution by reducing the effort required to document, reproduce, and troubleshoot the defects generated from automated tests.

Jonathan Lindo
Three Components of Effective Defect-Management Systems

Software development teams and software testing teams have numerous defect-management tool choices to help support their software defect efforts. But, selecting and utilizing an effective tool is really only part of an overall defect-management system.

Krishen Kota
Fuzzing Through the Side Door

Fuzz testing, or "fuzzing,” is an approach to test automation that attempts to uncover weaknesses in a system using tool-generated data. In this article, Jonathan Kohl recounts how he used this technique on a published web services interface to test “through the side door”—those testable, in-between areas like messaging APIs.

Jonathan Kohl's picture Jonathan Kohl
9 Questions You Must Ask When Selecting the Right Tool and Vendor

The key to selecting the best vendor and tool is asking the right questions. The answers to these nine essential questions can mean the difference between satisfaction with your purchase and a giant waste of time and money.

Joe Townsend's picture Joe Townsend
People, Processes and Tools: The Three Pillars of Software Development

Every project is dependent upon people, processes, and tools:  they are how the work gets done. These three essential elements are not equal, though, as each has its own strengths and weaknesses.   Each one provides a different value to our projects.


Alan S. Koch
Beware the IDE: The Risks of Standardizing on One IDE

Two topics that are likely to launch a development team into an impassioned discussion are development standards and development environments (IDEs, editors, etc). Combining the two topics into that of standardizing on development environments, is even more likely to spark debate. Decisions about development tools affect the day to day workings of each person on the team as well as the productivity of the team, and as such are important to discuss as a team organizes itself.

A Word with the Wise: Assessment First with David Dang

David Dang, a senior practice manager for Questcon Technologies, explains why you need think about the tool you select. According to Dang, the assessment of the project and its goals should always come first in test automation projects, otherwise, you risk maintainability issues down the road.

Joey McAllister's picture Joey McAllister
A Word with the Wise: Expanding Testing Horizons

In this Sticky ToolLook interview, Danny Faught shares insight onto his earliest days as a tester, the skills he's acquired throughout his career, and skills and tools he believes every tester should posses.

Joey McAllister's picture Joey McAllister
How Audit Trails and Traceability Mitigate Risk

Traceability doesn't prevent errors and an audit trail does little to help me to recover from one. Does this mean they aren't valuable CM tools? On the contrary, audit trails and traceability are two of our most important CM tools for learning how to mitigate risk.

Alan S. Koch
Toolsmiths-Embrace Your Roots

People have been automating software development, testing, and deployment processes since the stone age of software. The toolsmith of today shares a lot in common with these ancestral automation efforts. In this week's column, Danny Faught details how toolsmiths can learn by studying the computer subcultures of the past and present that are similar to their own.

Danny R. Faught's picture Danny R. Faught


StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.