Jump to content

Cucumber (software)

From Wikipedia, the free encyclopedia
(Redirected from Gherkin (language))
Cucumber
Developer(s)Aslak Hellesøy,[1] Joseph Wilk,[2] Matt Wynne,[3] Gregory Hnatiuk,[4] Mike Sassak[5]
Stable release
9.1.2[6] Edit this on Wikidata / 7 May 2023; 11 December 2023; 16 January 2024
Repository
Written inRuby
Operating systemCross-platform
TypeBehavior driven development framework / Test tool
LicenseMIT License
Websitecucumber.io

Cucumber is a software tool that supports behavior-driven development (BDD).[7][8][9][10][11][12] Central to the Cucumber BDD approach is its ordinary language parser called Gherkin. It allows expected software behaviors to be specified in a logical language that customers can understand. As such, Cucumber allows the execution of feature documentation written in business-facing text.[13][7][8] It is often used for testing other software.[14] It runs automated acceptance tests written in a behavior-driven development (BDD) style.[15]

Cucumber was originally written in the Ruby programming language.[7][16][8] and was originally used exclusively for Ruby testing as a complement to the RSpec BDD framework. Cucumber now supports a variety of different programming languages through various implementations, including Java[17][8] and JavaScript.[18][19] There is a port of Cucumber to .NET called SpecFlow,[20][21][22] now superseded by Reqnroll.[23]

Gherkin language

[edit]

Gherkin is the language that Cucumber uses to define test cases. It is designed to be non-technical and human readable, and collectively describes use cases relating to a software system.[7][8][24][25] The purpose behind Gherkin's syntax is to promote behavior-driven development practices across an entire development team, including business analysts and managers. It seeks to enforce firm, unambiguous requirements starting in the initial phases of requirements definition by business management and in other stages of the development lifecycle.

In addition to providing a script for automated testing, Gherkin's natural language syntax is designed to provide simple documentation of the code under test.[25] Gherkin currently supports keywords in dozens of languages.[25][26][7][8]

Syntax

[edit]

Syntax is centered around a line-oriented design, similar to that of Python. The structure of a file is defined using whitespace and other control characters.[25] Lines starting with # are considered comments, and can be placed anywhere in a file.[25] Instructions are any non-empty and non-comment line. They consist of a recognized Gherkin keyword followed by a string.[27]

All Gherkin files have the .feature file extension. They contain a single Feature definition for the system under test and are an executable test script.[27]

Here is an example of the syntax:[28] 

Feature: Guess the word

  # The first example has two steps
  Scenario: Maker starts a game
    When the Maker starts a game
    Then the Maker waits for a Breaker to join

  # The second example has three steps
  Scenario: Breaker joins a game
    Given the Maker has started a game with the word "silky"
    When the Breaker joins the Maker's game
    Then the Breaker must guess a word with 5 characters

Command line

[edit]

Cucumber comes with a built-in command line interface that covers a comprehensive list of instructions. Like most command line tools, cucumber provides the --help option that provides a summary of arguments the command accepts.[29] 

$ cucumber --help
        -r, --require LIBRARY|DIR        Require files before executing the features.
        --i18n LANG                      List keywords for in a particular language.
                                         Run with "--i18n help" to see all languages.
        -f, --format FORMAT              How to format features (Default: pretty).
        -o, --out [FILE|DIR]             Write output to a file/directory instead of
        ...

Cucumber command line can be used to quickly run defined tests. It also supports running a subset of scenarios by filtering tags. 

$ cucumber --tags @tag-name

The above command helps in executing only those scenarios that have the specified @tag-name.[29] Arguments can be provided as a logical OR or AND operation of tags. Apart from tags, scenarios can be filtered on scenario names.[29] 

$ cucumber --name logout

The above command will run only those scenarios that contain the word 'logout'.

It is also useful to be able to know what went wrong when a test fails. Cucumber makes it easy to catch bugs in the code with the --backtrace option.[29]

References

[edit]
  1. ^ "Aslak Hellesøy". Aslakhellesoy.com. Retrieved 2012-01-24.
  2. ^ "Joseph Wilk | on AI, The Web, Usability, Testing & Software process". Blog.josephwilk.net. Retrieved 2012-01-24.
  3. ^ "Tea-Driven Development". Blog.mattwynne.net. Retrieved 2012-01-24.
  4. ^ "ghnatiuk's Profile". GitHub. Retrieved 2012-01-24.
  5. ^ "msassak's Profile". GitHub. Retrieved 2012-01-24.
  6. ^ "Release 9.1.2". 7 May 2023. Retrieved 30 May 2023.
  7. ^ a b c d e "The Pragmatic Bookshelf | The Cucumber Book". Pragprog.com. Archived from the original on 2012-01-21. Retrieved 2012-01-24.
  8. ^ a b c d e f Rose, Seb; Wynne, Matt; Hellesøy, Aslak (15 February 2015). The Pragmatic Bookshelf | The Cucumber For Java Book. Pragprog.com. Retrieved 2019-04-28.
  9. ^ "What is Cucumber?". cucumber. Retrieved 2019-06-08.
  10. ^ Aslak Hellesøy. "The world's most misunderstood collaboration tool". cucumber.
  11. ^ Nagy, Gáspár; Rose, Seb (2017-03-07). The BDD Books - Discovery. Leanpub. ISBN 978-1983591259.{{cite book}}: CS1 maint: date and year (link)
  12. ^ Rose, Seb; Nagy, Gáspár (2021-04-27). The BDD Books – Formulation. Leanpub. ISBN 979-8723395015.{{cite book}}: CS1 maint: date and year (link)
  13. ^ Fox, Armando; Patterson, David (2016). Engineering Software as a Service. Strawberry Canyon. pp. 218–255. ISBN 978-0-9848812-4-6.
  14. ^ "Automated testing with Selenium and Cucumber". www.ibm.com. 2013-08-06. Retrieved 2017-02-09.
  15. ^ Soeken, Mathias; Wille, Robert; Drechsler, Rolf (2012-05-29). Furia, Carlo A.; Nanz, Sebastian (eds.). Objects, Models, Components, Patterns. Lecture Notes in Computer Science. Springer Berlin Heidelberg. pp. 269–287. doi:10.1007/978-3-642-30561-0_19. ISBN 9783642305603.
  16. ^ "The Pragmatic Bookshelf | The RSpec Book". Pragprog.com. 2010-12-02. Archived from the original on 2012-01-21. Retrieved 2012-01-24.
  17. ^ "Cucumber-jvm". cucumber. Retrieved 2018-03-08.
  18. ^ "Cucumber-js". cucumber. Retrieved 2018-03-08.
  19. ^ Naidele Manjunath; Olivier de Meulder (2019-02-01). "No Code? No Problem — Writing Tests in Plain English". Times Open. Retrieved 2019-04-29.
  20. ^ "Binding Business Requirements to .NET Code". SpecFlow. Retrieved 2019-04-29.
  21. ^ "SpecFlow". GitHub. Retrieved 2019-04-29.
  22. ^ Richard Lawrence; Paul Rayner (2018). Behavior-Driven Development with Cucumber. Addison Wesley.
  23. ^ Nagy, Gáspár. "From SpecFlow to Reqnroll: Why and How". reqnroll.net. Reqnroll. Retrieved 18 April 2024.
  24. ^ "cucumber/gherkin". GitHub. Retrieved 2017-02-09.
  25. ^ a b c d e "Gherkin Syntax". cucumber. Retrieved 2019-07-09.
  26. ^ "Gherkin Supported Languages". Gherkin. cucumber/cucumber: Cucumber monorepo - building blocks for Cucumber in various languages. Retrieved 2021-03-21 – via GitHub.
  27. ^ a b "Reference". cucumber. Archived from the original on 2015-10-25. Retrieved 2016-01-17.
  28. ^ "Gherkin Reference". cucumber. Archived from the original on 2024-01-13. Retrieved 2024-02-11.
  29. ^ a b c d Wynne, Matt; Hellesoy, Aslak. "The Cucumber Book". SafariBooksOnline. Retrieved 22 January 2016.
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Cucumber_(software)&oldid=1252165255#Gherkin_language"