Migration plan for a lettuce or aloe implementation #1207
-
I have an application with BDD tests originally written with lettuce and then migrated to some awful fork called aloe. Both libs are pretty much dead. I see behave is the only still maintained cucumber implementation and it seems well accepted in the community. The only reference I fond so far is this paragraph of data (notice the link for lettuce is no longer valid, you may not want to keep linking to it!): Is there any definitive guide or scripts that help migrating from lettuce to Behave? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
I am not aware of any tool that converts a
DIFFERENCES:
SEE ALSO:
NOTES:
|
Beta Was this translation helpful? Give feedback.
-
Or ask ChatGPT or its equivalents, like:
|
Beta Was this translation helpful? Give feedback.
I am not aware of any tool that converts a
lettuce
project to abehave
project.Therefore, you probably need to do that by hand (at least initially).
DIFFERENCES:
behave
supports a number of step-matchers.parse
is the default one,cucumber-expressions
is the newest. You normal make a decision which one is used per project or per step-library (as default step-matcher). All except the regex step-matcher have type-conversion support for the parameters.lettuce
(if I remember it correctly)SEE ALSO: