Versions Compared

Old Version 3

changes.mady.by.user Sergio Freire

Saved on

compared with

New Version Current

changes.mady.by.user Sergio Freire

Saved on

Key

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

...

Section
Column
width50%

The following diagram briefly illustrates the purpose of each entity.

Column
width50%

Tests are written to validate requirements, or any other coverable issue.  Optionally, they can be complemented with Preconditions, as means to specify the initial conditions to be assured before Tests can be run. Tests and Preconditions address test designing.


Concerning organization (i.e. the way that Tests are organized in the context of some project), Xray gives two approaches: one is list-based, abstracted as Test Sets issues; and the other is hierarchical, abstracted as the Test Repository (which is not an issue type).


Tests that are to be validated at a certain time for a certain target of the SUT (e.g., version, sprint) can be tracked in Test Plans.


Tests can be scheduled for execution by creating assignable “tasks” called Test Executions. They contain the list of Tests along with the recorded result (i.e., for each Test, the Test Execution contains a Test Run). They can be created in an ad hoc way or in a planned way (i.e., linked to some Test Plan(s)). The results of planned Test Executions will be visible and consolidated on the linked Test Plan(s).

 


Test Set vs. Test Plan

While Test Sets address organization, Test Plans address planning. Thus, they have different purposes.

...

A Test Set does not provide any direct information related with test results.

Image Added




A Test Plan, on the other hand, tracks the results of some Tests in some version/sprint of the SUT. Thus, its purpose is to identify the Tests you want to run, to schedule executions for them and then group the respective results.

Thus, a Test Plan can be seen as a higher-level entity above Test Executions. It groups multiple Test Executions and presents a consolidated overview (i.e., the latest status) for the Tests tracked within it.


Image Added


For a given version, or a given sprint, you may create one or more Test Plans to track the test results related to different tests (e.g., you may create a Test Plan for regression testing and another one for non-regression testing).

...