Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This gadget provides a way to see the evolution of a group of Tests in some a particular version of the system by taking into account some given certain Test Executions.

Table of Contents

Aim

Purpose

This gadget enables you to see, at a glance, See the evolution/trend of the current status of a group of Tests, taking into account the results from of those Tests in some given certain Test Executions.

This report allows the user to see the The calculated status (e.g.. , TODO, PASS, FAIL, etc.) of the Tests per day , i.e. the amount of Tests by their current execution status, on a daily basis.is shown.

Possible Some possible usage scenarios:

  • see the progress of the calculated status of some certain Tests for some a specific version;
  • see the progress of the calculated status of some certain Tests for some a specific version , on some a specific Test Environment;
  • see the progress of the calculated status of the Tests in a given Test Plan, taking into account the Test Executions related associated with the Test Plan.

How to use


Note
titlePlease note

The performance of this gadget will be mostly affect by the amount of Test Runs from the given Test Executions. Please use this gadget wisely.

...

Start by selecting the Tests and the Test Execution issues with:

  • Saved Filter for Tests:  A a saved filter containing Test Issues
  • Saved Filter for Test Executions:  A a saved filter containing Test Execution Issues

You can also restrict futher the Test Runs that will be used for the calculation of the values.

  • Date Range: either Custom or Time frame
    • if "custom"Custom, the then you need to provide the dates of the time period:
      • Start date and End date:  Only only the Test Runs with start date and end date between this range will be considered
    • if "time Time frame", then it can be either:
      • Current Week
      • Last Week
      • Current NonthMonth
      • Last Month
  • Test Run Assignee:  The Assignee of the user assigned to the Test Run
  • Test Run Status: The the status of the Test Run
  • Test Environment:  The the Test Environment to take into account (i.e., only consider the Test Runs from Test Executions made for this environment)

It is also possible to configure the:

  • Custom Title:  A custom a specific title for the gadget
  • Number of results:  The the number of results per page
  • Refresh Interval:  The rate at which how often the gadget will be is updated


Info
titlePlease note

Please note that only the selected/filtered Test Runs from the given Test Executions are taken into account for account in the calculation of the status of the Tests for a any given moment in time.

This means that only those Test Runs are considered. Therefore If, as an for example, if 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

The Tests Evolution gadget alows you to see the evolution/trend of Tests over time, which may occur due to new executions made for those Tests or to changes made to the reported statuses in the existing Test Runs.

Threrefore, this gadget does its calculations 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.

It also takes into account the setting "Final statuses have precedence over non-final statuses" setting, which is available under "Manage Test Statuses" in the Xray settings.


General rules for the calculation of the status at for a given day

  • changes Changes made over time to the status of a Test Run will be reflected in the calculated status calculated for that Test  (no matter if regardless of whether it's a final or a non-final status).
  • a A status will " persist " (be i.e., valid) from the moment it has been recorded until the next status change in that Test Run or in another Test Run.
  • the "The Started on" or the "Finished on" dates of the Test Runs are not taken into account for the calculation.
  • note that Test Runs are only created whenever when you start executing them; therefore, if you create a Test Execution and don't execute the respective corresponding runs, then you won't see them being reflected in this gadget.

"Final statuses have precedence over non-final statuses" checked

scenarioScenarioyesterdayYesterdaytoday Today 10amtoday Today 11am
1

TR1

TR1

-Test Run
PASSTO DOTODO-status change made in that day
PASSTO DOTODOcalculated Test status for that day

2

TR1

TR1TR1Test Run
PASSFAILTO DOTODOstatus change made in that day
PASSTO DOTODOcalculated Test status for that day
3TR1TR2-Test Run
PASSTO DOTODO-status change made in that day
PASSPASScalculated Test status for that day
4

TR1TR2
Test Run
PASSFAIL
status change made in that day
PASSFAILcalculated Test status for that day
5-TR1
Test Run
-PASS
status change made in that day
-PASScalculated Test status for that day

...

In this case, all statuses are considered independently if independent of whether they are final or not. The key differentiator is that  latest test runs are run is always considered, just by taking into account their the creation date.

   

scenarioScenarioyesterdayYesterdaytoday Today 10am

today Today 11am


1

TR1

TR1

TR1Test Run
PASSFAILTO DOTODOstatus change made in that day
PASSTO DOTODOcalculated Test status for that day
2TR1TR2TR2Test Run
PASSFAILTO DOTODOstatus change made in that day
PASSTO DOTODOcalculated Test status for that day
3

-TR1TR2Test Run
-FAILPASSstatus change made in that day
-PASScalculated Test status for that day
4TR1TR2-Test Run
TO DOTODOPASS-status change made in that day
TO DOTODOPASScalculated Test status for that day

...