Page History
...
| Gliffy Diagram | ||||
|---|---|---|---|---|
|
Summary of features per framework
...
Robot framework | Junit 4 | Nunit 2.6/3.x | Cucumber | Xray JSON | |
|---|---|---|---|---|---|
Abstract automated test as a Test (map an automated test to a Test issue in JIRA) | Yes (as a Generic Test) | Yes (as a Generic Test) | Yes (as a Generic Test) | Yes (as a Cucumber Test) | No. Tests must exist beforehand. |
Make Test specification in JIRA (specify the Test itself in JIRA) | No | No | No | Yes | Yes |
Create Tests from results (create Tests whenever importing results) | Yes | Yes | Yes | No* (however, tehre is and endpoint for importing Cucumber features, which will create Tests for the respective Scenarios/Scenario Outlines) | No |
Uniquely identify Tests (identify existing Tests whenever importing results, avoiding duplication of Test issues) | Yes | Yes | Yes | Yes | Yes* (based on the provided Test issue keys) |
Import results (importing results by REST API or UI) | Yes | Yes | Yes | Yes | Yes |
Import “labels” (create labels in the Test issues) | Yes (labels may be specified in the test's source code) | No | Yes (labels may be specified in the test's source code) | Yes* (this is only available whenever using the endpoint for importing Cucumber features; it's not possible whenever importing results) | No |
Automatic linking to requirements (create links to requirements) | Yes (requirement's issue key may be specified in the test's source code) | No | Yes (requirement's issue key may be specified in the test's source code) | Yes* (this is only available whenever using the endpoint for importing Cucumber features; it's not possible whenever importing results) | No |
Semantic on the results (present detailed execution details in the execution screen) | Yes (keywords “steps”) | - | Yes (Test Suites & parameterized Tests) | Yes (steps for scenario/scenario outline and background) | Yes* (semantic is implicit, because the Test must be created beforehand) |
Integration by platform
|
|  |
|
|  |
|
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
Integration by testing framework report
|
|  | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
...
Testing by target environment
| Browser testing | Mobile Testing | Testing in the Cloud | ||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
|
...