One Step Back ... Two Steps Forward

Better Software Magazine
By
Michael Bolton
-
January 30, 2007
Volume-Issue: 
2007-02
Article Summary: 

A change to code that previously was working may introduce new failures. Testing for regression can catch these failures, find new problems, and identify opportunities to improve your test design.

TechWell Stories
To Estimate or Not to Estimate—That Is the Question
Removing Waste in Software Projects
Create a Vendor Contract While Keeping Agile
How Agile Teams Use DevOps for Deployment
Build a List of Things—But Don't Call It Agile

Upcoming Events

Jun 02 Agile Development Conference & Better Software Conference West
The Complete Picture

Recommended Web Seminars

May 23 Key Principles to Mobile Performance Testing
May 29 How to Integrate Performance Testing into Agile and Hybrid Environments
Jun 11 Test Infrastructure Changes as Easy as Pressing Play
Jun 18 Adopting Agile and Moving into the Future
On Demand 7 Habits of Highly Effective Agile Teams

Featured Resources

» Skytap Automation Pack for Microsoft VS Team Foundation Server | Skytap
» An Innovative Approach to Integration Testing | IBM Rational
» Improve Quality and Decrease Time to Market with Requirements Management | PTC
» Cloud-Enabled Software Development and Testing | Skytap
» Performance Testing in the Cloud | J9 Technologies