Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement] Integration with Xray #2108

Closed
glassalle59 opened this issue Mar 10, 2020 · 6 comments
Closed

[Enhancement] Integration with Xray #2108

glassalle59 opened this issue Mar 10, 2020 · 6 comments

Comments

@glassalle59
Copy link

glassalle59 commented Mar 10, 2020

Hello From Montreal !

I want to use both Xray (Jira plugin) and Cerberus

Xray intregrates well some automation tools like Cucumber or Robotframework

I would like to get the execution of the report of each Cerberus test to display on the corresponding test in Xray

Documentation Xray :

https://confluence.xpand-it.com/display/public/XRAY/Integrating+with+Testing+Frameworks

Anyone here already use both of these tools together ?

Sincerly,

@glassalle59 glassalle59 changed the title Integration with Xray [Enhancement] Integration with Xray Mar 17, 2020
@glassalle59
Copy link
Author

@vertigo17
Copy link
Member

vertigo17 commented Dec 28, 2021

If I describe the use case:
For each Cerberus Campaign, I can link it to an XRay Test Plan (No longuer required as the Execution is automatically created at the 1st Cerberus execution). On XRay side, No need for a Test Plan in order to create an Execution.
For each Cerberus Test Case, I can link it to an XRay Test. (Using the External provider JiraXray-Cloud or JiraXray-DC + External Reference to the JIRA Epic reference)
Once this is done, when I start a Campaign execution on Cerberus side, it will acutomaticaly create the Test Execution on XRay side. For every Test Case added to the campaign execution, Cerberus will add on XRay side the corresponding Run attached to each Test.

I start to list here the dev to perform:

  • Allow to edit from Test Case modal and link each Test Case with External referencial XRAY + Reference.
  • Added Parameters to setup Xray Cloud (clientId and Secret) and Xray DC (URL and token).
  • On each last retry execution update XRAY with corresponding result + save the Link to JIRA Epic on Tag table

NB1 : The 1st call to Xray creates the Execution on JIRA side and store the reference inside the tag. If several execution finish at the same time, only the first one create the execution, the others are on hold until JIRA provide the reference so that all others are attached to the same Execution.
NB2 : When in Cloud mode, the token is saved in cache. It can the reset by calling the manageV001 API.

Questions to answer:
If Cerberus create several execution per country, environnement and robot, should Cerberus still update the last execution submited (On XRay side there will be only 1 Test to update) ?
Answer: Yes and it will be the last one triggered by Cerberus.

@vertigo17 vertigo17 self-assigned this Jun 13, 2022
vertigo17 added a commit that referenced this issue Jul 17, 2022
New purgeCache action on manageV001 API
@vertigo17
Copy link
Member

vertigo17 commented Oct 24, 2022

TODO:

  • Fix status mapping for DC connectivity to: PASS, FAIL, EXECUTING, BLOCKED, ABORTED
  • Enrish testEnvironments sections with list of env and countries
"testEnvironments": [
   "prod",
   "FR-Default"
]

@vertigo17
Copy link
Member

A DC mapping issue was fixed with commit

@MathisSenicourt
Copy link
Contributor

New fixe with commit

@vertigo17
Copy link
Member

fixed from release 4.17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants