When developing a software product, multiple versions will be released. With the continuous maintenance of test cases, the test cases will be continuously improved and the product features and features (features) so the test case is associated with the product version. In particular, for software products that provide software services, multiple versions often coexist to provide services to customers. In this case, multiple versions of test cases coexist, therefore, you must be very careful when creating, modifying, and deleting test cases, and have corresponding rules.
Based on the consistency between the product features and test case, the solution is divided into the following situations:
1. the product features remain unchanged, but test case can be improved based on the late discovery bug or remedy ticket. The test case can only be modified at this time, which means that the test case is currently modified, it is valid for both current and previous versions.
2. the original product features have changed, not new feature, but enhanced features (Feature Enhancement). At this time, the original test case is only valid for previous versions (such as version 1.0 and 2.0, the new version (such as version 3.0) is invalid. In this case, you must add a new test case instead of modifying the test case. This is important. The original test case is still valid for the original version (such as version 1.0 and 2.0 ).
3. The original function is canceled. In this case, you only need to set the corresponding test case to inactive (invalid) in the new version ).
4. Completely new features are added. It is clear to you that the corresponding and new test cases are added.