Page History
...
Start by selecting the Tests and/or the Test Execution issues with:
- Saved Filter for Tests: a saved filter containing Test Issues
- Saved Filter for Test Executions: a saved filter containing Test Execution Issues
You can define one of these filters or both. If you just define the "Saved Filter for Tests", then the execution trend for those Tests will be shown, no matter in which Test Execution they were run. On the other hand, if you only define the "Saved Filter for Test Executions" then the execution trend will be shown for the Tests that are part of those Test Executions, in the scope of those Test Executions.
If both filters are defined, then the execution trend is shown just for the Tests contained within the "Saved Filter for Tests", taking into account the runs from the Test Executions identified by the "Saved Filter for Test Executions".
You can also restrict the Test Runs that will be used for the calculation of the values.
- Date Range: either Custom or , Time frame or Planned dates from Test Executions
- if "Custom", then you need to provide the dates of the time period:
- Start date and End date: only the Test Runs with start date and end date between this range will be considered
- if "Time frame", then it can be either:
- Current Week
- Last Week
- Current Month
- Last Month
- if "Planned dates from Test Executions", then the minimum and maximum of begin and end dates, respectively, from the Test Executions are considered
- if "Custom", then you need to provide the dates of the time period:
- Test Run Assignee: the user assigned to the Test Run
- Test Run Status: the status of the Test Run
- Test Environment: the Test Environment to take into account (i.e., only consider the Test Runs from Test Executions made for this environment)
...
| Info | ||
|---|---|---|
| ||
Please note that only the selected/filtered Test Runs from the given Test Executions are taken into account in the calculation of the status of the Tests for any given moment in time. This means that only those Test Runs are considered. If, for example, some Test was PASS (because you already had executed it somewhere in the past and the latest status of it was PASS) but you're only taking into account some more recent runs, then it will start by showing as TODO at the start of the chart. |
How it works
Calculations are based on the historical changes for the Test Runs being considered. Note that for a given Test Run you may or not change the Test Run statuses several times; this gadget will consider it.
...