email2vimalraj / CucumberExtentReporter

A plugin to generate the cucumber jvm custom html report using ExtentsReport
http://www.vimalselvam.com/cucumber-extent-reporter/
MIT License
58 stars 75 forks source link

"STEPNAME" are wrong when there are several scenarios in the same feature #2

Closed dmtraining closed 8 years ago

dmtraining commented 8 years ago

Hello,

When I'm trying to run a feature file including several scenarios ("Scenario Outline" in my case), the "STEPNAME" column of the report file are wrong.

The steps names related to the 1st scenario are correct but not for the other ones. In the section related to the 2nd scenario, I can see the steps name of the 1st scenation first and after, the ones related to the 2nd scenario.

Example - Scenario 1 (3 steps) Given Scenario1_StepName_1 When Scenario1_StepName_2 Then Scenario1_StepName_3

Example - Scenario 2 (5 steps) Given Scenario2_StepName_1 When Scenario2_StepName_2 And Scenario2_StepName_3 Then Scenario2_StepName_4 And Scenario2_StepName_5

The report file will be like that for the scenario 1

STATUSTIMESTAMPSTEPNAMEDETAILS
  Scenario1_StepName_1 
  Scenario1_StepName_2 
  Scenario1_StepName_3 

The report file will be like that for the scenario 2

STATUSTIMESTAMPSTEPNAMEDETAILS
  Scenario1_StepName_1 
  Scenario1_StepName_2 
  Scenario1_StepName_3 
  Scenario2_StepName_1 
  Scenario2_StepName_2 

Could you please help to fix this issue?

Thanks.

dmtraining commented 8 years ago

Hi @email2vimalraj ,

Could you please help me?

Thanks.

email2vimalraj commented 8 years ago

@dmtraining : I'll have a look and get back to you.

email2vimalraj commented 8 years ago

@dmtraining : I confirm there is an issue. I'll work on fix and update you.

dmtraining commented 8 years ago

Thanks @email2vimalraj. I'm waiting for your update :-)

email2vimalraj commented 8 years ago

This issue is fixed now and will be part of the next release.

email2vimalraj commented 8 years ago

@dmtraining : The issue has been fixed as part of the new release v1.1.0. Kindly update your pom and execute again.

Feel free to re-open in case the issue is not solved.