Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

XRay Cucumber Test Case API overwriting manual test cases

I'm using this endpoint /rest/raven/1.0/import/feature?projectKey={{projectKey}} to create and update cucumber test cases, following the documentation here https://docs.getxray.app/display/XRAY/Importing+Cucumber+Tests+-+REST

 

In our project we have a combination of manual and cucumber tests, often a manual test and cucumber test will test the same functionality so they will have the same name. An issue we're seeing is if a manual test is created and we attempt to upload a new cucumber test case via the api with the same name, the manual test is being overwritten with the details of the cucumber test. Our cucumber test cases are identified using the @id tag, not the test case id.

 

The logic of selecting which test case to update in this api is documented as follows:

  1. try to find the Test by key, if found then update it; else...
  2. try to find the Test having:
    1. a label with the original relative path of .feature (e.g. "core/sample_addition.feature)
    2. a label named "id:xxx", where xxx is some number (e.g. "id:1", "id:32"); this label comes from a scenario/scenario outline's tag
    3. no other label ending in ".feature"
  3. try to find the Test having:
    1. a label with the original relative path of .feature (e.g. "core/sample_addition.feature)
    2. the same summary
    3. no other label ending in ".feature"
  4. try to find the Test having:
    1. the same Summary
    2. no label ending in ".feature", except the one corresponding to the relative path of the Cucumber file being imported
  5. create Test in that project and add a label with the relative path of the feature. The tags used in the scenario/scenario outline are also added as labels.

 

I believe that we should be hitting option 5 to create a new test case but the api seems to be identifying a manual test with the same summary, can anyone provide insight into this? is it a bug?

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

How to log work and track time in Jira when a person is part of multiple teams

  The manager’s daily activities include a list of challenges to reach high levels of efficiency for their teams. Part of these challenges is related to how to deal with the worklog systems sin...

102 views 2 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you