Testing in the Dark How can you test software without knowing what it should do? Here is a step-by-step approach to overcoming undocumented requirements, including how to discover the requirements, how to define "quality" for the project, and how to create a test plan including release criteria. |
||
The Test Matrix: How to Keep a Complex Test Project on Track When testing needs to account for different user environments and installation configurations, the possible combinations can add up quickly. Read how one company used a simple data organization method to keep everything on track. |
Mark Pawson
June 26, 2002 |
|
Karl Wiegers Describes Ten Requirements Traps to Avoid Recognized requirements expert, Karl Wiegers, shares the symptoms and solutions for common requirements-related project problems, including inadequate customer involvement, vague and ambiguous requirements, inadequate change process, and scope creep. |
Karl E. Wiegers
June 26, 2002 |
|
Managing Your ERP Project Managing your ERP Project |
Marie Benesh
June 26, 2002 |
|
On-Track Requirements: How to Evaluate Requirements for Testability Prior to using the requirements to develop the Test Plan, an analysis should be performed to evaluate the testability of the requirements. This article suggests a proven method used on a recent project that accomplishes such an evaluation. |
Rodger Drabick
June 26, 2002 |
|
Evaluating Tools You, or perhaps your manager, have decided that it's time to choose a tool. Where do you begin? How do you go about comparing them? This article provides a five-step process for comparing, evaluating, and finally choosing the right tool for your organization. |
||
Software Configuration Management Pat Wegerson recommends software configuration management resources AntiPatterns and Patterns in Software Configuration Management and the online CM Yellow Pages. |
||
Agile Development Technical Editor Brian Marick explains the values behind the Manifesto for Agile Software Development. Above all, Agile practitioners value: individuals and interactions; working software; customer collaboration; and responding to change. |
Brian Marick
June 26, 2001 |
Pages
Upcoming Events
Oct 13 |
Agile + DevOps USA The Conference for Agile and DevOps Professionals |
Apr 27 |
STAREAST Software Testing Conference in Orlando & Online |