Closed mefateah closed 4 years ago
Could be accomplished via ITestTracer
(TechTalk.SpecFLow.Tracing), which should be registered as test thread dependency in container. But we need a way how to avoid overriding of default registered object.
Our current approach of reporting is based on hooks, which is not very good. This issue requires full re-implementation of plugin. Awaiting advice from https://github.com/techtalk/SpecFlow/issues/1394
For some reason after upgrading NUnit and ReportPortal related libs: ReportPortal.Client ReportPortal.NLog ReportPortal.Shared ReportPortal.SpecFlow I faced that skipped steps are not shown in a test report. For example I run the following scenario from example project:
Scenario: Add three numbers Given I have entered 3 into the calculator And I have entered 7 into the calculator And I have entered 8 into the calculator When I press add Then the result should be 18 on the screen
and made the scenario to fail in 'And I have entered 7 into the calculator' step then I don't see all steps after the failed one but in a previous version I've seen them as skipped
I have the same issue using NUnit 3. Could you receive this problem, please?
What was your previous version of ReportPortal.SpecFlow
package you didn't meet this issue with?
@nvborisenko It worked with the following lib packages versions: "NUnit" version="2.6.4" "ReportPortal.Client" version="1.2.3" "ReportPortal.NLog" version="1.1.8" "ReportPortal.Shared" version="1.4.1" "ReportPortal.SpecFlow" version="1.2.1" "SpecFlow" version="2.1.0"
CucucmberMessages
might help.
For some reason after upgrading NUnit and ReportPortal related libs: ReportPortal.Client ReportPortal.NLog ReportPortal.Shared ReportPortal.SpecFlow I faced that skipped steps are not shown in a test report. For example I run the following scenario from example project:
and made the scenario to fail in 'And I have entered 7 into the calculator' step then I don't see all steps after the failed one but in a previous version I've seen them as skipped