Versions Compared

Key

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

...

The Xray JSON format is more generic and its capabilities, if used for importing, are different.



Robot framework

JUnit 4

TestNG

NUnit 2.6/3.x

CucumberXray 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 Generic Test)

Yes

(as a Cucumber Test)

No

Tests must exist beforehand

Make Test specification in Jira

(specify the Test itself in Jira)


NoNoNoNoYesYes

Create Tests from results

(create Tests whenever importing results)

Yes

Yes

Yes

Yes

No*

(but there 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

Yes*

(based on the provided Test issue keys)

Import results

(importing results by REST API or UI)

Yes

Yes

Yes

Yes

YesYes

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

(labels may be specified in the test's source code)

Yes*

(this is only available when using the endpoint for importing Cucumber features; it's not possible when 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

(requirement's issue key may be specified in the test's source code)

Yes*

(this is only available when using the endpoint for importing Cucumber features; it's not possible when importing results)

No

Semantic on the results

(present execution details in the execution screen)

Yes

(keyword “steps”)

-

Yes

(DETAIL)

Yes

(Test Suites and parameterized Tests)

Yes

(steps for Scenario/Scenario Outline and Background)

Yes*

(semantic is implicit, because the Test must be created beforehand)

Integration by platform

Image result for java logo

Image result for php logo transparent



Content by Label
showLabelsfalse
showSpacefalse
sorttitle
cqllabel = "java" and space = currentSpace()
labelsjava

Content by Label
showLabelsfalse
showSpacefalse
sorttitle
cqllabel = "csharp" and space = currentSpace()
labelscsharp

Content by Label
showLabelsfalse
showSpacefalse
sorttitle
cqllabel in ("c++","c") and space = currentSpace()
labelsc++,c

Content by Label
showLabelsfalse
showSpacefalse
sorttitle
cqllabel = "javascript" and space = currentSpace()
labelsjavascript

Content by Label
showLabelsfalse
showSpacefalse
sorttitle
cqllabel = "ruby" and space = currentSpace()
labelsruby

Content by Label
showLabelsfalse
showSpacefalse
sorttitle
cqllabel = "php" and space = currentSpace()
labelsphp

Content by Label
showLabelsfalse
showSpacefalse
sorttitle
cqllabel = "python" and space = currentSpace()
labelspython

Content by Label
showLabelsfalse
showSpacefalse
sorttitle
cqllabel = "perl" and space = currentSpace()
labelsperl


...