Skip to content

Attributes are not reflected at Suite Level when Serenity Tests are triggered #193

@rakshitjain25

Description

@rakshitjain25

Hi,

We are using Serenity BDD framework and leveraing ReportPortal for our execution.
While working on the segregation of the TCs at feature level, we observed that attributes are not getting reflected at suite level. Rather it is reflected at the test level.

Scenario - Lets say we have a feature file(Feature:V4 Unplug Testing) where at the top we are passing @issue:ECPXLR-1234 and in another feature file(Feature:SCA Scanning Testing) we are passing @issue:ECPXLR-4444

So when the Tests are triggered, we wanted to see the issues being passed as attributes at the suite level in RP but we see that its blank.

Can you please check or suggest how we can achieve this?

image image

PS - We are using below dependencies/versions -

com.github.invictum
serenity-reportportal-integration
1.6.2

<serenity.version>4.1.0</serenity.version>

Thanks
Rakshit

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions