Background introduction
Project to be online immediately, the function has been completed 80%, not in the complete requirements of the document, only scattered stories, but due to the process and various reasons, has been no test personnel involved. The test case should be written in a short time and conform to the specifications and requirements of the general use case.
Practice Process
- Comb the test case template to confirm with the customer whether the coverage of the template meets the requirements
- 2 hours to communicate with BA business process, understand the whole project business process and function point carding.
- Use 3-4 hours, combining the functions of the project with the story, self-organizing and refurbishing the function points of the business process (using mind mapping software). Check with BA to see if there is a missing core function
- 2-3 hours, write a test case that completes a module. Confirm with the customer whether there is a complete procedure for the omission and coverage of the function. How much coverage of the synchronization adjustment case
- 2 days to finish writing the remaining use cases. Submit Customer Audits
Summarize
- Gain early access to the core functions of the system to understand the overall system's process trend
- In the process of writing use cases, if there is ambiguous place, find the BA communication in time
- Use case template coverage, to find customer confirmation as early as possible. Less cover before the template, resulting in rework
- Self-grooming business process and function points, easy to repair the system function understanding and coverage is very important .
How to write test cases efficiently
