flutter_gherkin icon indicating copy to clipboard operation
flutter_gherkin copied to clipboard

Unnamed scenario in the report

Open umangdivyanshu opened this issue 2 years ago • 4 comments

If I have multiple feature files and I am running scenarios by specifying the tags. If I do not include the first scenario from any of the feature file then it is being reported as unnamed scenario in the report.

For e.g. I have 3 scenarios in my login feature file. Whenever I am excluding the first scenario, there is one unnamed scenario coming in the report before the two executed scenarios. Also the feature name is Unnamed Feature and marked as Failed in the report.

image

image

image

umangdivyanshu avatar Jul 11 '22 11:07 umangdivyanshu

Hi @jonsamwell,

Could you please take a look on this issue?

umangdivyanshu avatar Jul 20 '22 17:07 umangdivyanshu

What version of the library are you using? Can you provide a sample repo to reproduce this issue? Thanks.

On Thu, Jul 21, 2022, 3:28 AM umangdivyanshu @.***> wrote:

Hi @jonsamwell https://github.com/jonsamwell,

Could you please take a look on this issue?

— Reply to this email directly, view it on GitHub https://github.com/jonsamwell/flutter_gherkin/issues/248#issuecomment-1190555840, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4F7IMHYJ5NYUIQNE32ORTVVAZKRANCNFSM53HH72UA . You are receiving this because you were mentioned.Message ID: @.***>

jonsamwell avatar Jul 20 '22 17:07 jonsamwell

Hi, I don't know if the cause is the same as @umangdivyanshu, but I also get this error when the first test is not run. For example, I have 3 tests in a feature with these tags:

@AddPhotos @ios Scenario: ...

@AddPhotos @Android Scenario: ...

@RemovePhotos Scenario: ...

When I run tests on Android with "not @ios" tags, the first test is not run, as expected, but I get an unnamed feature and an unnamed first test in the report.

I use the packages flutter_gherkin 3.0.0-rc16.

If my problem is not the same as this, I can create a new issue.

Stephane99 avatar Jul 21 '22 15:07 Stephane99

What version of the library are you using? Can you provide a sample repo to reproduce this issue? Thanks.

I am using 3.0.0-rc9 but the same issue is observed on 3.0.0-rc16 as mentioned by @Stephane99 in above comment

umangdivyanshu avatar Jul 27 '22 08:07 umangdivyanshu