Multiple Scenarios in Report Portal If we call a Scenario in another Feature

[Shivin89]

Hi @kirksl

When we run our tests, we see called scenarios ( Scenarios called from another feature file ) also in Report Portal. But I want to see only Scenarios that I have run ( not the called scenarios, that should be steps inside the test scenario)

Hierarchy in Report Portal should be :

Launches > Features > Scenarios (Main Test Scenario) > steps and steps of reusable (Called scenario steps)

In the below Image, Roadster Store Login and other scenarios below that are called scenarios from another feature file and the main scenario is "Quotes Comparison for Cash"

This is the code

• def login = read('classpath:com/cdk/reusable_hooks/roadsterStore_Login.feature@login')

  @Basic_Cash Scenario Outline: Cash with Basic Test

• call login
• delay(2000)

What changes Should we have to make?

Thanks Shivin Saraf

[kirksl]

Hi @Shivin89. This is indeed something that would be great to fix. I unfortunately haven't had the time to investigate a proper solution. Happy to take a pull request from you if you can solve this. One idea might be to update the logic in RPReporter at the link below which essentially determines the status off the Scenario. Updating it to keep the status as SKIPPED would throw those tests into a SKIPPED bucket within ReportPortal which could be ignored. Alternatively just avoid reporting those tests back to ReportPortal. The bigger thing to solve would be to determine if the target scenario has been called by another scenario which would be logic to figure out within Karate.

https://github.com/kirksl/karate-maven-gradle/blob/master/src/test/java/RPReporter.java#L271

[kirksl]

Closing due to inactivity