search

reportportal / agent-net-gauge

Reporter plugin for https://gauge.org
Apache License 2.0
12 stars 5 forks source link

Tags on specification level are not applied to scenario level #38

Closed elenkuz closed 3 years ago

elenkuz commented 3 years ago

Preconditions:

  1. Gauge runner is used.
  2. There is a specification with two test scenarios: specification has its own tags and each test scenario also has its tags.

gauge_specification_with_tests

Actual Result: In Report Portal in each test scenario there is only its own tag present (e.g. android-case-id:5555) without tags from specification (owner: SomeTeam, tag:android).

specification_in_rp

tests_tags_actual

Expected Result: In Report Portal in each test scenario there are all tags from specification + tags from test scenario. So tags for one test should be next: android-case-id:5555, owner: SomeTeam, tag: android.

test_ tags_expected

item_details_expected_result

nvborisenko commented 3 years ago

Tags for specification comes to specification in RP.

image

Looking forward any other opinions whether we need duplicate specification tags at scenario level.

Dmitriy85 commented 3 years ago

Tags for specification comes to specification in RP.

image

Looking forward any other opinions whether we need duplicate specification tags at scenario level.

The idea is to have relation between scenario and specification tags. For example I have tag owner:Jim - on spec level, I'd like to be able to link this owner to all scenario names inside this specification. Hope it makes sense to you @nvborisenko

nvborisenko commented 3 years ago

Personally I don't mind. Why not.

Dmitriy85 commented 3 years ago

@nvborisenko any updates, any ETA?

nvborisenko commented 3 years ago

No ETA, I do it when time allows me

dnet1 commented 3 years ago

From the Gauge documentation on tags:

Both scenarios and specifications can be separately tagged, however, only one set of tags can be added to a single specification or scenario. A tag applied to a spec automatically applies to a scenario as well.

So I believe it makes sense to have the same logic in reportportal plugin.