π What did you see?
Running a suite with steps that return godog.ErrPending in subtest mode fails the test regardless of the Strict option.
β
What did you expect to see?
Running a suite with steps that return godog.ErrPending in subtest mode:
- fails the test if the
Strict option is set to true
- does not fail the test (maybe skips with
t.Skip()) if the Strict option is set to false
π¦ Which tool/library version are you using?
Godog v0.12.6
Golang v1.19.4 darwin/amd64
π¬ How could we reproduce it?
- Create a simple feature with at least one step
- Create a subtest mode test to run the feature, setting the
Strict option to false
- Run the test to get the generated stubs
- Copy-paste the output into the appropriate places in the test file
- Run the test again - the subtest is marked as failed.
π Any additional context?
If the TestingT parameter is removed then the Strict flag behaves as I'd expect.
Raising as an issue as I'm not 100% sure if this behaviour's intentional. If accepted, am happy to contribute a fix.
This text was originally generated from a template, then edited by hand. You can modify the template here.
π What did you see?
Running a suite with steps that return
godog.ErrPendingin subtest mode fails the test regardless of theStrictoption.β What did you expect to see?
Running a suite with steps that return
godog.ErrPendingin subtest mode:Strictoption is set to truet.Skip()) if theStrictoption is set to falseπ¦ Which tool/library version are you using?
Godog v0.12.6
Golang v1.19.4 darwin/amd64
π¬ How could we reproduce it?
Strictoption tofalseπ Any additional context?
If the
TestingTparameter is removed then theStrictflag behaves as I'd expect.Raising as an issue as I'm not 100% sure if this behaviour's intentional. If accepted, am happy to contribute a fix.
This text was originally generated from a template, then edited by hand. You can modify the template here.