trivago / cluecumber

Clear and concise reporting for the Cucumber BDD JSON format.

Home Page:https://www.softwaretester.blog

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Show (filtered) tags on the scenario summary page

codingHahn opened this issue · comments

Is your feature request related to a problem? Please describe.
I tag every scenario with its corresponding issue number (e.g. @issue_2342). I want to see this tag on the scenario summary page.

Describe the solution you'd like
A new column titled tags with an optional filter would be best. I only want to see the tags that start with "issue". This filter could be specified at compile time.

Describe alternatives you've considered
none

I already have the new column in my fork. How should the tag filter be implemented, considering that there is already a tagFilter in the code?

I intentionally wanted to keep the scenario summary as decluttered as possible. For tags, there is already the "all tags" page that enables searching and filtering for specific tags and going directly to scenarios with a specific tag.

Would you accept it if it would be implemented as a configuration parameter?

Even if this were available as a config parameter, the resulting view would look horrible when scenarios have multiple tags. This seems like an edge case that is specific to your requirement. Also, because there is already a tag specific page available with similar functionality, I would rather not accept it.

I understand. This is a niche use case. Another question: How do I make the example project use the local cluecumber for generating the report?

If you have a local version built, it should be in your local maven (.m2) directory. Once it is there and has the same or a newer version as the "official" version, it should be automatically used from there.

Thanks!