Versions Compared

Key

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

...

  • the Comment field which contains any notes about the corresponding step;
  • the Defects field which contains any defect associated with the corresponding step. It is also possible to input new defects by:
    - Clicking on the Create Defect to create a new Defect
    - Clicking on the Create Sub-Task to create a new Sub-Task
    - Clicking on the Add Defects to add an already existing defect
  • the Evidences field which contains any attachment associated with the corresponding step. It is also possible to input new attachments by clicking on the + button, which opens the Attach Files dialogue box
  • the Status which contains the current step testing status. This can be changed by clicking on any of the status in front of your Step Status.

Note: Changing the Status on the each Step will affect the Execution Status field on the Execution Screen.

Image RemovedImage Added

Automated Test Details

An Automated Test execution screen contains the Automated Test Details field, which list the Steps to be used as reference by the external tool while testing.

Image RemovedImage Added

Examples

A scenario outline of an automated Cucumber test will normally contain an examples table containing several inputs and outputs for the given scenario.

The examples section details these examples, containing an overall status bar in the header and a table with all the examples below. Each example can have the status: PASS, FAIL, EXECUTING or TODO. 

A scenario outline test is PASS only if all examples passed.

...

A scenario outline test is TODO if at least one of the examples did not run and all the other examples passed or todo.

Image RemovedImage Added

Results

Xray for Jira supports the import of multiple execution results for the same Test Run. Multiple execution for the same Test Run specify different results for different context/environments. Multiple executions are only supported for Automated Tests. Manual Tests do not have this concept.

...

  • Context: An execution context name (in the case of Xamarin Test Cloud results, the mobile device and operating system version) 
  • Error Message: A possible error message if the result has failed.
  • Duration: The complete duration of an execution result.
  • Status: The execution results status.


Image RemovedImage Added

Attaching Screenshots

To attach a screenshot, paste the image from your clipboard using the relevant keyboard shortcut. (For Mac OSX, use CMD+V; for Windows, use Ctrl+V.)

Image RemovedImage Added

Enter a file name for the screenshot you are attaching (defaults to "screenshot-" concatenated with the next number available) and choose where you want to place the evidence (Overall Execution or Test Steps).

Image RemovedImage Added

Click UploadSave to attach the captured image to your Test Run.

...

The Activity field lists all the activities related with the current execution.

Image RemovedImage Added

Updating the definition of the Test after execution started

When a Test definition has changed, a new dialog box will appear on the top of the Execution page informing you that the current execution is obsolete, and will prompt you with Reset or Merge buttons that, when pressed, will load the updated definition as well as delete all the execution data or merge the new Test definition into current state of execution. 

Image RemovedImage Added

Reset Execution

...