grey-rain
commented
10 months ago @aprado94 I know its been a while, but I made some digging here.
The issue you face comes from Serenity itself: they do not distinct story-level tags (long TTL) from example-level tags (short TTL) in net.thucydides.model.domain.TestOutcome#addTag and it just accumulates all tags it faced during execution. In can be seen in native Serenity report, they also have this tag applied to all 3 tests.
If you're still interested in having this issue resolved - please report it to Serenity team (https://github.com/serenity-bdd/serenity-core/issues/new/choose) or propose a fix.
Integration will be fixed as soon as the issue is fixed in Serenity and new Serenity version is wrapped into integration.
I am using Serenity with Cucumber and what I am trying to do is dividing the scenario examples with different tags like in the following image:
When the tests are uploaded to the Report Portal something strange seems to be happening related to the tag management. In my scenario outline examples, I used 3 different tags for each test example: example1, example2 and example3. But when I check the tests in the Report Portal, the first one has the correct tag, but the following examples have their corresponding tag and the previous example tag.
What I was expecting to happen, was that each test example would have its related tag attached and not taking the attribute value from itself and all the previous ones, so in this case 3 examples will be tagged as example1, 2 as example2, and 1 as example3.
Could this be a bug related to this integration?