Hey everyone! I’m new to using Cucumber for my project testing. So far, I’ve managed to create HTML, JSON, and XML reports. But here’s the thing: I really want to show JIRA IDs next to each feature in the report. It would make it so much easier to track things.
I’ve been searching online, but I can’t seem to find a straightforward way to do this. Has anyone done something similar before? Or do you know of any plugins or tricks that could help?
It would be awesome if I could just click on a feature in the report and see the related JIRA issue. Any ideas or suggestions would be super helpful!
Thanks in advance for your help. I’m excited to learn more about Cucumber and make our testing process even better!
hey, i tink adding jira ids as tags is a neat trick. you can annotate feature files with tags like @JIRA-123 and then use or build a custom formatter to link them. not flawless but does the job. good luck!
I’ve been using Cucumber for a while, and I’ve found a workaround that might help. Instead of trying to modify the Cucumber reports directly, we use a post-processing step in our CI pipeline. We’ve written a simple script that parses the Cucumber JSON output and our JIRA export, then generates a new report with the JIRA links included.
It’s not perfect, but it gets the job done. The key is to have a consistent naming convention for your features that includes the JIRA ID. For example, we prefix our feature names with the JIRA ticket number.
One caveat: this approach requires a bit of maintenance, especially if your JIRA structure changes. But overall, it’s been a game-changer for our team’s traceability. If you’re comfortable with a bit of scripting, it might be worth exploring this route.
I’ve faced a similar challenge in my projects. One effective approach is to utilize Cucumber’s custom formatters. You can develop a formatter that extracts JIRA IDs from your feature file comments or tags and incorporates them into the report. This method requires some coding, but it offers flexibility in how you present the JIRA references.
Another option is to explore third-party plugins. Some CI/CD tools have integrations that can link test results with JIRA issues. While not directly part of Cucumber, these can provide the traceability you’re seeking.
Remember, the key is consistency in how you reference JIRA issues within your feature files. Establish a clear convention for your team to follow.