Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Cucumber Transforms. Should they work this way? #1055
Cucumber Transforms don't behave as one would expect. Having searched around for various bits of information, we have a hacky work-around in place here. Which allows us to use them (As they are intended to be), but doesn't allow us to have more complex ones.
If you "explicitly call"
Cucumber searches through the
This is exacerbated when you then apply functions to the transforms, such as basic class changers (
Sadly I'm not huge into my development. So the only proposed solution would be for the Expected Behaviour to work
Steps to Reproduce (for bugs)
In order to re-produce this, you need two Transforms that either match on the same regex, or similar regex. You could have the following two - and you would only ever be able to run
Every time you call either
Context & Motivation
Self explanatory really. It would be nice to start using more indepth regex. And cucumber is really lovely.
Additional info links:
referenced this issue
Aug 31, 2017
Hi Matt. I'll definitely give it a whirl (You released the 3.0.0.pre1 for us to try the retry formatter.
Honest question. Why is there an issue (Or what is happening under the hood). That makes cucumber not force itself to use the expression I type. In my eyes it's a bit misleading. Below is the kind of analogy (Albeit comical I face)
Me to cucumber: I want cucumber to use transform A