<aside> 💡 Perform the Functional Test to check the User Interface and User Experience of a build. Think of this as an expanded version of your internal test before doing the Sprint Review.
</aside>
<aside> 💡 Provide a brief project introduction and documentation purpose.
</aside>
The Hybrid Project Management using Waterfall and Agile project aims to establish an end-to-end process supplemented with tools to guide users on how to implement based on a hybrid method.
<aside> 💡 Fill in this matrix for every new test scenario.
</aside>
<aside> 💡 Click the Add a New Functional Test Scenario button to add a new template.
</aside>
| Project Name | |||
|---|---|---|---|
| Functional Test ID | Provide a unique Functional Test Scenario ID | ||
| Test Name | Provide a unique Functional Test Scenario Name | ||
| Functional Design Mapping | Provide the Functional Design Specification where this test is related to | ||
| Sprint | Identify the Sprint(s) where this test will be executed | ||
| Release | Identify the Release(s) where this test will be included | ||
| Created On | DD/MM/YYYY | ||
| Last Update | DD/MM/YYYY | ||
| Author | Last Name, First Name | ||
| Tester Name | Last Name, First Name | ||
| Overview | Brief description of the test scenario | ||
| Expected Results | Describe the output expected for this scenario to pass | ||
| Step No. | Description | Pass or Fail Y/N | Tester Notes |
| 1 | Describe the step to test this scenario | Describe steps to replicate (for Failed cases), restrictions, conditional pass requirements, etc. | |
| 2 | |||
| 3 | |||
| 4 | |||
| 5 |
| Version | Date | Author | Role | Description |
|---|---|---|---|---|