Cross platform parser for the Gherkin language. Used by Cucumber to parse .feature files.
https://github.com/cucumber/cucumber/wiki/Gherkin or https://cucumber.io/docs are really good places to start.
You will need to decide in what language your framework will be coded. I suggest getting the developers input here, That will naturally lead you to the appropriate cucumber flavour you need.
That is cucumber's solution as per the text book.
Behat, I have never tried. But if that is what suites your application then go for it.
You can use scala with cucumber too
The important thing to realise here is that cucumber is a documentation layer. The code that runs the tests is your framework layer. Keep those independent.
It will mean less pain later
Sorry for the vague answer, but it shouldn't be someone else's call as we do not know all the intricate details of how your project functions. You do, therefore, you are best qualified to make that call :)
You should should use the same programming language in your step definition/framework layer as your application does, and choose the flavor of Cucumber based on that:
Ruby -> Cucumber-Ruby
Javascript -> Cucumber-JS
Languages on the JVM -> Cucumber-JVM
C# -> Specflow
PHP -> Behat
Python -> Behave
Ruby -> Cucumber-Ruby
Javascript -> Cucumber-JS
Languages on the JVM -> Cucumber-JVM
C# -> Specflow
PHP -> Behat
Python -> Behave
I dont fully agree with that. Even more so in a micro service architecture. With microservices one of the benefits is to use the language appropriate for that service. So you could have a complete mix of languages. Given this is a user workflow automation suite it should be considered as its own project/service and by that should also be free to dictate whatever tools/languages it needs to get the job done.
@Freyskeyd if you're testing the UI, I'd assume you're also testing that it looks nice, can click buttons etc. If you're testing the process (i.e. as user can log in, order a product, get a confirmation - you don't have to do that through the UI). But starting at the UI is what most people do when they come from manual testing, it's the natural starting point. It's fine; just be aware there are other options
Unless you're using Cypress.io which talks to the browser differently
But it's javascript and I don't javascript that well...
@Freyskeyd Your example scenario might not be the best to automate through the UI though. I might start with some simpler ones
Also, I know many people don't like Selenium, not sure of better alternatives (apart from possibly Cypress.io). In my experience this also has a lot to do with unstable xpaths etc. So my main tip there would be to get the developers to add unique labels to the UI elements you need for your tests (or better yet, do it yourself if you can ;) to you can operate on those, even if the screen layout changes. We do that and our tests through the UI are relatively stable...
Ofcourse, if the application is developed by a different company, you can't do it that way
Oh I should add that my project is an angular app, so it would be a bit heavy to use a library not on npm (a ruby gem for example)
@lwouis
A few gherkin linters that I have used.
https://github.com/funkwerk/gherkin_lint (idle)
https://github.com/r-cochran/cuke_sniffer (abandoned)
And a tool that I use when the 'out of the box' linters don't cover my needs and I need to write custom lints/queries.
https://github.com/enkessler/cql
@jenisys If I have a step such as Given <Args.jenkinsbuild> is present. The parameter here would be changing with every build, so using a step table or example table would not be ideal is what I am thinking? Is there any other way? It is my understanding that the step impl. will use the value given for the parameter and not get the value from somewhere and be able to set it in the step? please advise
@yelisetti This functionality is not available in Gherkin. You would need to use a text-template engine to generate the feature files from your parameter space. Otherwise, it is rather easy to use such parameters in the step implementation, but it is harder to show these parameters in Gherkin (output).
Hi together, I have a question to gherkin or better to build the gherkin project. I wanted to add a new gherkin dialect and some new keywords. From the contributing to Gherkin page I get not enough information about how to customize or expand the actual gherkin. Can you help me?
Especially what kind of steps do I have to do?
Especially what kind of steps do I have to do?
@Patrick You mean to ass a new language ? Add a record to gherkin-languages.json file and provide a pull-request on Github. see https://github.com/cucumber/cucumber/blob/master/gherkin/gherkin-languages.json
@jw2121 https://github.com/cucumber/cucumber/blob/master/gherkin/gherkin.berp — This the URL to the Gherkin grammar that is currenly used. In the subdirectories are language implementation of a Gherkin parser in this language. Look at the Java implementation and start from there.