You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In short, the Two-way step navigation doesn't work with the re step parameter parser.
My team tried out the re step parser (see Behave Docs). I'm able to run my tests as expected, but if I look at the .feature file, the steps that make use of the re parser are shown in red and can't be matched to their step definitions (ie, pressing F12 doesn't take me to the definitions).
# myfeature.featureFeature: my featureScenario: check the cameraGiven the camera is enabled
Then the camera is enabled
# steps.pyuse_step_matcher("re")
@given("the camera is (?P<status>enabled|disabled)")defgiven_camera_status(context: Context, status: str) ->None:
# Do some stuff@then("the camera is (?P<status>enabled|disabled|disconnected)")defthen_camera_status(context: Context, status: str) ->None:
# Do some stuff
Describe the solution you'd like
I'd love to be able to use Two-way step navigation with my regex parameter steps.
The text was updated successfully, but these errors were encountered:
In short, the Two-way step navigation doesn't work with the
re
step parameter parser.My team tried out the
re
step parser (see Behave Docs). I'm able to run my tests as expected, but if I look at the .feature file, the steps that make use of there
parser are shown in red and can't be matched to their step definitions (ie, pressing F12 doesn't take me to the definitions).Describe the solution you'd like
I'd love to be able to use Two-way step navigation with my regex parameter steps.
The text was updated successfully, but these errors were encountered: