Versions Compared

Old Version 7

changes.mady.by.user Unknown User (lfir)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (tdda)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
UI Steps
UI Step

What is the Test Run Status

The state or result that was reported against a Test Run

  • Represents the status of the Test in the context of some Test Execution
  • Can be set explicitly/inline or automatically, based on the step level results (i.e. statuses)



Warning

The Test Run Status it is not the TestRunStatus custom field (this is a totally different thing explained ahead). 

UI Step

Test Status Configuration


Xray provides some built-in Test Step statuses (which can’t be modified nor deleted). 


But you can add at based on your own tastepreference. 


Info
  • Custom statuses may be created in Xray administration settings
    • A status may be marked as “final” 
    • Able to specify how the status contributes to the calculation of the requirement/coverage status
  • Ranking is used to compare statuses under certain circumstances (explained ahead)
UI Step

Where can you view it?

Usually referred as “Status”

  • Execution screen itself (“execution status”)
  • Test Runs panel (in Test issue screen, Test Execution issue screen)
  • Traceability report
  • Test Runs List report/gadget



UI Step

Computing the overall status of a Test Run

  1. Use existing Test Run status if it has been enforced manually, otherwise proceed
  2. Obtain the test status mapped to each reported test step status
  3. Compare  all the the previous mapped test statuses together
    1. Any status wins over PASS
    2. FAIL wins over any status
    3. Statuses marked as “final” win over intermediary ones
    4. Use ranking of mapped test statuses 

Image Added

How ranking end up being applied. 

Gliffy Diagram
macroIdeef6e286-cad9-4c2f-814b-78ddb732a92f
nameStatus Calculation
pagePin1



Warning

If all mapped statuses are only a mix of TODO and PASS, then consider Test Run to be EXECUTING