The Testing tab holds the project's test plan and its results. Open it from the project menu: Delivery, then Testing.
What it's for
Testing answers one question for go-live: does the system do what the business needs? The tab groups tests into scenarios (a business process to test, such as order to cash) and test cases (the individual steps and expected results). It shows how many have passed, failed or are blocked in each test cycle, and which WRICEF objects have no test at all.
Seven figures sit at the top: Total scenarios, Total test cases, Passed, Failed, Blocked, Not executed and Pass rate. Pass rate is passed cases divided by passed plus failed cases, so cases not yet run do not drag it down.
Test cycles
Every scenario and case belongs to a cycle: Unit test, SIT (system integration testing), UAT (user acceptance testing), Regression, Performance or Cutover dry run. The buttons above the scenarios filter the page to one cycle.
Before you start
Before you build the test plan
- The project's plan includes Testing (Professional, Enterprise or a personal plan)
- Your role can create tests
- WRICEF objects are in the register, so cases can be linked to them
- You know which cycle you are planning for
How to add scenarios and test cases
- Add a scenario
Select Add scenario. Enter a Title, choose the Test cycle, and add the Description, Business process, Workstream, Owner, Priority and Notes.
- Add test cases
Select Add test case. Enter a Title, pick the Parent scenario and Test cycle, and write the Preconditions, Test steps and Expected result.
- Link to WRICEF
Choose the Linked WRICEF object the case proves, and the Tester and Priority.
- Save
The app gives each case an ID such as ABC-TC-014.
How to record a result
- Open the case
Select the test case from its scenario.
- Record what happened
Fill in the Actual result and Execution date, then set Status to Passed, Failed, Blocked, In progress, Deferred or Not executed.
- Describe a failure
If the case failed, a Defect description field appears and is required.
- Raise the defect
Once the failed case is saved with a defect description, select Create issue. The app creates an issue titled Test Defect with the case's title, with a severity taken from the case's priority, and links it to the case. See Issues.
Checking coverage
Open WRICEF test coverage to see every WRICEF object with its number of test cases and how many passed, failed or were not executed. Once you link cases to objects, any object without a case shows Zero coverage in red, so gaps are easy to spot. See WRICEF objects.
Two charts show progress over time: Execution trend (cases executed and passed, cumulative by week) and Pass and fail by cycle.
Good to know
- Cases that do not belong to a scenario are listed under Test cases without a scenario.
- Testing needs Professional, Enterprise or a personal plan. A project manager can also hide the tab for a project in its settings. See Plans and pricing.
Who can do this
Admins, project managers, test managers, functional leads and technical leads can create and edit scenarios and cases. Consultants can execute tests and record results. Only admins, project managers and test managers can delete tests. See Roles and permissions.