We are using Xray plugin for JIRA for managing our automated tests for Cucumber. When exporting the .feature-files from Xray, the feature name is blank. Like in this example:
Hi @majchman,
that behaviour is currently hard-coded, so it takes the summary from the "requirement" issue.
Having it taken from the test summary I guess it wouldn't work, since you may be exporting multiple tests at the same time, but this has to be properly evaluated. I would ask you to open an improvement request in our project in JIRA, detailing the exact behavior, so it can be analyzed and we also see feedback from other users.
Please use Xray's service desk so we can properly track and give you on time feedback.
Regards,
Sergio
Even after linking the requirement with the test, the feature name is blank in exported cucumber files.
One thing i have noticed is that our project is not listed as "Requirement" project in admin. Is it necessary to enable that to get feature names in exported cucumber files?
This is important as we generate multiple feature files for parallel execution using cucumber-jvm-parallel, but without a feature name, all scenarios(as "Test" issue type) in a test set end up in a single feature file prolonging execution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
yes, you must enable requirement coverage on that project.
You may do it from the Requirements Projects administration tab settings or from the project settings page as mentioned here: https://confluence.xpand-it.com/display/XRAY/Quick+Setup
If you still face issues, please reach our support so they can help you out.
Regards
Sergio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
If we are exporting multiple tests from X-Ray, can we just hard code the feature description to something like "Multiple Tests from X-Ray" or anything. We are running our tests via serenity and absence of Description is causing our builds to fail.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Rahul_Kasana ,
sorry but I missed this message.
No, you can't harcode the feature description. It is filled automatically from the requirement's description. If the tests are not linked to any requirement, it will generate an invalid .feature file (missing the "Feature: " section). We may improve this in the near future to have there a dummy feature like "Feature: default".
As I've mentioned, you can and should reach out our support team in the future; they will be glad to help you out. Here's the service desk link.
Regards,
Sergio
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your reply, I am good for now. I have added a step to modify the downloaded feature file to insert something like "Feature: As a bamboo agent I want to run tests from xyz" before actually starting with the test execution.
Regards,
Rahul
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.