Refer to the actual project or requirement document when writing test cases? _ Testing Technology

The writing of test cases is an indispensable and important part of the test process, but we are writing the use cases according to the actual project or according to the requirements document as the standard.


In a company of a certain size, there must be a job, the test case review, after the test case design is complete and before the test begins. The project director, the project developer, the product personnel, and the visual interaction personnel, all of the project's related personnel sit together, the tester initiates, together carries on the test case review, and the review's best time point is after the project has started, completes the partial coding work, Then, on the basis of the test cases written by the tester against the requirement document, the team members further check the details of the project requirements, and if there are inconsistencies in the understanding, they can discuss and reach an agreement immediately. Because the project is still under development, if the differences in the function is not yet developed is naturally the best; even if the function has been developed, the cost of modification is much lower than the completion of the development, so the requirements of the document to ask the standard test case design and carding is the need to filter again, The review process is a clean-up of the demand dispute point, which can greatly improve the accuracy of requirements and reduce unnecessary development costs.