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
I'd like to execute this just to check the feature files are well-formed (from a Gherkins/Cucumber point of view).
This is to automatically validate a merge-request of .feature files modifications, without having to run these heavy .feature files.
It's the first layer of safety.
Currently, Karate ignores this Cucumber flag.
Or perhaps a special mode that would also check there is no "compilation" error on the syntax of JavaScripts and JsonPaths without running them... But I think that would be complicated on your part, so I don't need this.
The text was updated successfully, but these errors were encountered:
this goes into "help wanted" as well considering also that no-one has ever requested this. I actually prefer your second option because I plan to drop cucumber at some point.
Oh! Do you have any idea of how Karate would look like without Cucumber? Will it still use Gherkin syntax? Will it be a super- or sub-set? What advantages? What removals? What additions?
the plan is to use our own parser, life-cycle and reports. but retain the existing syntax 100%. the challenge is for cucumber ide support to continue to work or we write our own. not going to happen very soon though.
On 23-Jun-2018, at 3:59 PM, slaout ***@***.***> wrote:
Oh! Do you have any idea of how Karate would look like without Cucumber? Will it still use Gherkin syntax? Will it be a super- or sub-set? What advantages? What removals? What additions?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
closing as duplicate of #444 - that ticket will be used to track the switch away from cucumber.
sounds like this is increasingly becoming an issue. only for folks having to mix Cucumber and Karate (yuck!) but still.
for those watching this list and reading the comments - can you help me understand if the Eclipse and IntelliJ Cucumber IDE support works fine with Cucumber 2.X and 3.X ?
I'd like to have a test with this:
@CucumberOptions(..., dryRun = true)
I'd like to execute this just to check the feature files are well-formed (from a Gherkins/Cucumber point of view).
This is to automatically validate a merge-request of .feature files modifications, without having to run these heavy .feature files.
It's the first layer of safety.
Currently, Karate ignores this Cucumber flag.
Or perhaps a special mode that would also check there is no "compilation" error on the syntax of JavaScripts and JsonPaths without running them... But I think that would be complicated on your part, so I don't need this.
The text was updated successfully, but these errors were encountered: