In this paper, I’ll do two things. First, I’ll attempt to demolish a bad model, the quite popular “V model”. In the process, I hope to banish the phrases “unit testing” and “integration testing” from our vocabularies. Second, I’ll describe a model I think is better. But my primary purpose is not to claim I have the right model – it’s too early for that – but to describe important requirements for test models that will replace mine. Those requirements are summarized at the end of the paper.

This paper describes a set of requirements tests that cover relevance, coherency, traceability, completeness and other qualities that successful requirements must have. The tests have their starting point with the criterion that each requirement has at least one quality measure. This measure is used to test whether any given solution satisfies, or does not satisfy, the requirement.

Execute Regression/Progression Tests. The primary purpose of regression testing is to prove that system enhancements, and routine tuning and maintenance do not affect the original functionality of the system. The secondary purpose is to prove that the enhance/maintenance changes do what they are intended to do, and do not do anything they are not intended to do.

It is possible to mitigate risk and speed up the process of adding new development to your legacy code by establishing a strategy to handle it. The strategy involves finding inflection points, applying test coverings, and refactoring code.

This article gives a complete description of code coverage analysis (test coverage analysis), a software testing technique.

Describes techiques (such as an in-memory database) for reducing the execution time and maintenance costs of automated regression test suites.

This article overviews the importance of, and strategies for, regression testing relational databases. If your organization considers data to be a corporate asset and/or you're implementing mission-critical functionality within your databases, shouldn't you have a database testing strategy in place?

The purpose of this step is to apply test case design techniques to design and build a set of "intelligent" test data. The data must address the system as completely as possible, but it must also focus in on high-risk areas, and system/data components where weaknesses are traditionally found (system boundaries, input value boundaries, output value boundaries, etc.).

To gain the most benefit from unit testing, you must understand its purpose and how it can help improve your software. In this chapter, you learn about the “universe” of software testing, where unit testing fits into this universe, and what its benefits and drawbacks are.

Analyze And Report Test Results. The purpose of the test report is to indicate which system functions work and which do not. This report should describe the level to which the system meets the test objectives. The report should include recommendations based on the success or failure of the system to meet the objectives.