Page History
...
You can either execute your tests manually or automatically. Even if the test is an automated test, you can manually set the test status for that execution.You can also create custom status statuses.
Tests are executed always within a Test Execution context, even if it's an ad-hoc execution. You can execute tests inline (i.e. define the test run status), directly in the Test Execution issue screen, or you can use the Execution Screen which is detailed extensively bellow in the next section.
...
The execution screen is composed by the following sections:
| Table of Contents |
|---|
Navigation bar
Always available, the navigation bar contains breadcrumbs to allow easy navigation between the Test issue hierarchy. It contains also a toolbar with the Return to Test Execution button, that allows to jump to the current Test Execution issue page, as well as the Next and Previous buttons, to quickly navigate to the execution screen of the other Tests included on the same Test Execution, if applicable.
Export Automatic Test Definition
...
If you're executing a Cucumber Test, an option to export the Test as feature file will appear.
Generic
If you're executing a Generic Test, then an option to export Test as test will appear.
Execution Status
The Execution Status describes the current Test progress. The possible (native) status for a Test Run are TODO, EXECUTING, FAIL, ABORTED and PASS. You can also create custom status in the Xray Manage Test Statuses Execute Tests administration page.
You can change the status of the execution directly through this field. It supports inline editing and once activated, it will display a set of statuses that you can set the Test Run. if the option for setting the Test Run status manually, without having to execute all Test Steps (or Examples in case of Cucumber Tests), is enabled in the Xray administration page, then you can set the Test Run Status to any status, independently of the current aggregate status of the Test Steps (or Examples). If this option is disabled, then the status that you can set through this field will be limited to the available transitions based on the current Steps or Examples aggregated statuses.
...
- Assignee, that shows the User assigned to perform the current test execution;
- Executed By, that shows the last User that changed the status of the current test run;
- Versions, that shows the target release version tested by the current test execution;
- Revision, that shows the source code and documentation version used in the current test execution;
- Started On, that shows the date of when the execution of the current test started;
- Finished On, that shows the date of when the execution of the current test finished;
You can change the Test Run assignee directly on the field. It supports inline editing and once activated you can filter by user and then select the one you wish to assign to the Test Run.
If the dates are configured to be edited, you can edit the Started On and Finished On dates by clicking in the calendar icon and choosing the date and time. You can check your configurations by going to JIRA ADMINISTRATION > Add-ons > Global Preferences.
Note: The JIRA jira.date.time.picker.java.format and jira.date.time.picker.javascript.format properties in JIRA Administration advanced settings should belong to the same pair of properties in order to the datetime picker work properly. See the following link for more information
...
| Info |
|---|
This section is only visible if the "Separation of Concerns" option is disabled in Xray Requirement Coverage administration page. |
All affected requirement statuses will be updated whenever a step (or example for cucumber automated Tests) status is changed. The status for any affected requirement can always be changed by clicking on the status and choosing the desired option.
...
The Execution Defects field lists the overall defects related with the current execution. It is possible to create a new Defect issue, create a new Sub-task or Add existing Defects by clicking on the respective option.
Execution Evidences
The Execution Evidences field lists the overall attachments related with the current execution and clicking on the Add Evidences, opens the Attach Files dialog box.
Comment
The Comment field is inline editable to input overall appreciations about the current execution without reloading the page
The field supports the JIRA markup wiki language.
Test Description
...
The field supports the JIRA markup wiki language.
Test Issue Links
This sections shows all links associated to the Test.
Test Issue Attachments
This sections shows all attachments associated to the Test.
Pre-Condition
The Pre-Condition field shows the Pre-Conditions issues associated with the current Test, if present.
Pre-Condition Attachments
The Pre-Condition field also shows the Pre-Conditions attachment in a inline dialog.
Manual Test Step Results Table
...
Changing the Status on the each Step also affects the Execution Status field on the Execution Screen.
Automated Test Details
A Automated Test execution screen contains the Automated Test Details field, listing the Steps to be used as reference by the external tool while testing.
Examples
A scenario outline of an automated Cucumber test with a will normally contain an examples table containing several inputs and outputs for the given scenario.
...
A scenario outline test is TODO if at least one of the examples is not run and all the other examples are passed or todo.
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 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 for an execution result.
- Status: The execution results status.
Attaching Screenshots
To attach a screenshot paste the image from your clipboard using the relevant keyboard shortcut. (For Max OSX use CMD+V, for Windows use Ctrl+V)
Enter a file name for the screenshot you are attaching (The file name defaults to "screenshot-" concatenated with the next number available.) and choose where you want to place the evidence (Overall Execution or Test Steps).
Click Upload to attach the captured image to your Test Run.
...
The Activity field lists all the activity related with the current execution.
Updating definition of Test after execution started
When a Test definition has changed, a new dialog box will appear on the top of the Execution page, informing the user of the obsolete current execution, and prompting to a 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.
Reset Execution
...