Use Case of FEA516
- Author: Jiahui Pan
- Date / Version: 19/02/2024
User roles
- Tester: Responsible for conducting manual testing.
- Product Owner: Initiates and oversees the manual testing process.
- Developer: Receives feedback from manual testing for bug fixes and improvements.
Prerequisites / Conditions
- The application under test should be deployed in a testing environment.
- Test scenarios and test cases should be defined.
Use Case Diagram
Description of use case -eg. Modify existing request
- The Product Owner initiates the manual testing process by assigning test cases to the Tester.
- The Tester conducts manual testing by executing predefined test scenarios and test cases, exploring various functionalities and features of the application.
- During testing, the Tester identifies defects, usability issues, and potential improvements.
- The Tester documents the test results, including observed issues and feedback.
- The Tester communicates the findings to the Product Owner and Developer for review and action.
- The Developer receives feedback from the Tester and addresses identified issues through bug fixes or feature enhancements.
Exceptions
-
E1: If critical defects are identified during testing, the Tester immediately notifies the Product Owner and Developer for urgent resolution.
-
E2: If the testing environment is unstable or inaccessible, the testing process may be delayed or postponed.
Result
- The expected result of the use case is to improve the quality, reliability, and usability of the application through thorough manual testing, resulting in bug fixes and enhancements.
Use frequency
- The manual testing use case is executed periodically during the development lifecycle, typically before major releases, after significant changes, or as part of regression testing.
Additional information
- Manual testing complements automated testing efforts and provides valuable insights into the user experience and application behavior in real-world scenarios. Test documentation and feedback are essential for continuous improvement and maintaining the quality of the software product.
Sources
This wiki-document is based on the The public administration recommendations
Thans to the original authors.