This commit is contained in:
2020-10-06 14:27:47 +07:00
commit 586be80cf6
16613 changed files with 3274099 additions and 0 deletions

View File

@@ -0,0 +1,29 @@
feature:
title: Addition
language: en
line: 2
description: |-
In order to avoid silly mistakes
As a math idiot
I want to be told the sum of two numbers
scenarios:
-
type: scenario
title: Add two numbers
line: 7
steps:
- { keyword_type: 'Given', type: 'Given', text: 'I have entered 11 into the calculator', line: 8 }
- { keyword_type: 'Given', type: 'And', text: 'I have entered 12 into the calculator', line: 9 }
- { keyword_type: 'When', type: 'When', text: 'I press add', line: 10 }
- { keyword_type: 'Then', type: 'Then', text: 'the result should be 23 on the screen', line: 11 }
-
type: scenario
title: Div two numbers
line: 13
steps:
- { keyword_type: 'Given', type: 'Given', text: 'I have entered 10 into the calculator', line: 14 }
- { keyword_type: 'Given', type: 'And', text: 'I have entered 2 into the calculator', line: 15 }
- { keyword_type: 'When', type: 'When', text: 'I press div', line: 16 }
- { keyword_type: 'Then', type: 'Then', text: 'the result should be 5 on the screen', line: 17 }

View File

@@ -0,0 +1,18 @@
feature:
title: Feature with background
language: en
line: 1
description: ~
background:
line: 3
steps:
- { keyword_type: Given, type: Given, text: a passing step, line: 4 }
scenarios:
-
type: scenario
title: ~
line: 6
steps:
- { keyword_type: Given, type: Given, text: a failing step, line: 7 }

View File

@@ -0,0 +1,26 @@
feature:
title: Feature with titled background
language: en
line: 1
description: ~
background:
line: 3
title: |-
Some Background
title with
couple
of
| continuous |
"""
strings
steps:
- { keyword_type: Given, type: Given, text: a passing step, line: 10 }
scenarios:
-
type: scenario
title: ~
line: 12
steps:
- { keyword_type: Given, type: Given, text: a failing step, line: 13 }

View File

@@ -0,0 +1,18 @@
feature:
line: 1
title: Big PyString
scenarios:
-
type: scenario
line: 2
steps:
-
keyword_type: Then
type: Then
text: it should fail with:
line: 3
arguments:
-
type: pystring
text: "\n# language: ru\n\nUUUUUU\n\n2 scenarios (2 undefined)\n6 steps (6 undefined)\n\nYou can implement step definitions for undefined steps with these snippets:\n\n$steps->Given('/^I have entered (\\d+)$/', function($world, $arg1) {\n throw new \\Everzet\\Behat\\Exception\\Pending();\n});\n\n$steps->Then('/^I must have (\\d+)$/', function($world, $arg1) {\n throw new \\Everzet\\Behat\\Exception\\Pending();\n});\n\n$steps->Then('/^String must be \\'([^\\']*)\\'$/', function($world, $arg1) {\n throw new \\Everzet\\Behat\\Exception\\Pending();\n});"

View File

@@ -0,0 +1,20 @@
feature:
title: Feature N4
line: 1
description: ~
scenarios:
-
type: scenario
tags: [normal]
line: 4
steps:
- { keyword_type: 'Given', type: 'Given', text: 'Some normal step N41', line: 5 }
- { keyword_type: 'Given', type: 'And', text: 'Some fast step N42', line: 6 }
-
type: scenario
tags: [fast]
line: 9
steps:
- { keyword_type: 'Given', type: 'Given', text: 'Some slow step N43', line: 10 }

View File

@@ -0,0 +1,10 @@
feature:
title: Fibonacci
language: en
line: 1
description: |-
In order to calculate super fast fibonacci series
As a pythonista
I want to use Python for that
scenarios: ~

View File

@@ -0,0 +1,21 @@
feature:
title: Using the Console Formatter
language: en
line: 3
description: |-
In order to verify this error # comment
I want to run this feature using the progress format#comment
So that it can be fixed
scenarios:
-
type: scenario
title: "A normal feature #comment in scenario title"
line: 19
steps:
- { keyword_type: 'Given', type: 'Given', text: 'I have a pending step #comment', line: 21 }
- { keyword_type: 'When', type: 'When', text: 'I run this feature with the progress format #comment', line: 24 }
- { keyword_type: 'Then', type: 'Then', text: "I should get a no method error for 'backtrace_line'", line: 31 }

View File

@@ -0,0 +1,26 @@
feature:
title: Complex descriptions
language: en
line: 7
description: |-
Some description with
| table | row|
and
"""
"""
scenarios:
-
type: scenario
title: |-
Some
| complex | description |
"""
hell yeah
"""
line: 16
steps:
- { keyword_type: 'Given', type: 'Given', text: 'one two three', line: 22 }

View File

@@ -0,0 +1,7 @@
feature:
title: Some feature
language: en
line: 1
description: ~
scenarios: []

View File

@@ -0,0 +1,13 @@
feature:
title: Cucumber command line
language: en
line: 1
description: |-
In order to write better software
Developers should be able to execute requirements as tests
scenarios:
-
type: scenario
title: Pending Scenario at the end of a file with whitespace after it
line: 6

View File

@@ -0,0 +1,13 @@
feature:
title: Cucumber command line
language: en
line: 1
description: |-
In order to write better software
Developers should be able to execute requirements as tests
scenarios:
-
type: scenario
title: Pending Scenario at the end of a file with whitespace after it
line: 6

View File

@@ -0,0 +1,30 @@
feature:
title: Math
language: en
line: 1
description: |-
In order to avoid silly mistakes
As a math idiot
I want to be told the calculation of two numbers
scenarios:
-
type: scenario
title: Add two numbers
line: 6
steps: []
-
type: scenario
title: Div two numbers
line: 7
steps: []
-
type: scenario
title: Multiply two numbers
line: 9
steps: []
-
type: scenario
title: Sub two numbers
line: 12
steps: []

View File

@@ -0,0 +1,27 @@
feature:
title: Fibonacci
language: en
line: 1
description: |-
In order to calculate super fast fibonacci series
As a pythonista
I want to use Python for that
scenarios:
-
type: outline
title: Series
line: 6
steps:
- { keyword_type: 'When', type: 'When', text: 'I ask python to calculate fibonacci up to <n>', line: 7 }
- { keyword_type: 'Then', type: 'Then', text: 'it should give me <series>', line: 8 }
examples:
11: [ n , series ]
12: [ 1 , '[]' ]
13: [ 2 , '[1, 1]' ]
14: [ 3 , '[1, 1, 2]' ]
15: [ 4 , '[1, 1, 2, 3]' ]
16: [ 6 , '[1, 1, 2, 3, 5]' ]
17: [ 9 , '[1, 1, 2, 3, 5, 8]' ]
18: [ 100 , '[1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89]' ]

View File

@@ -0,0 +1,29 @@
feature:
title: "Some '#quoted' string"
language: en
line: 2
description: |-
In order to avoid silly mistakes
As a "#math" idiot
I want to be told the sum of two numbers
scenarios:
-
type: scenario
title: Add two numbers
line: 7
steps:
- { keyword_type: 'Given', type: 'Given', text: 'I have entered 11 into the calculator', line: 8 }
- { keyword_type: 'Given', type: 'And', text: 'I have entered 12 into the calculator', line: 9 }
- { keyword_type: 'When', type: 'When', text: 'I press "#add"', line: 10 }
- { keyword_type: 'Then', type: 'Then', text: 'the result should be 23 on the screen', line: 11 }
-
type: scenario
title: 'Div "#two" numbers # as'
line: 13
steps:
- { keyword_type: 'Given', type: 'Given', text: 'I have entered 10 into the calculator', line: 14 }
- { keyword_type: 'Given', type: 'And', text: 'I have entered # 2 into the calculator', line: 15 }
- { keyword_type: 'When', type: 'When', text: 'I press div', line: 16 }
- { keyword_type: 'Then', type: 'Then', text: 'the result should be 5 on the screen', line: 17 }

View File

@@ -0,0 +1,49 @@
feature:
title: test pystring
description: second line
language: en
line: 1
scenarios:
-
type: scenario
title: |-
testing py string in scenario
second line
line: 4
steps:
-
keyword_type: Given
type: Given
text: the pystring is
line: 7
arguments:
-
type: pystring
text: |-
Test store name
Denmark, Kolding
6000
-
type: outline
title: |-
testing py string in scenario outline
second line
line: 14
steps:
-
keyword_type: Given
type: Given
text: the pystring is
line: 17
arguments:
arguments:
-
type: pystring
text: |-
Test store name
Denmark, Kolding
6000
examples:
24: ['']

View File

@@ -0,0 +1,21 @@
feature:
title: '加算'
keyword: 'フィーチャ'
language: ja
line: 2
description: |-
バカな間違いを避けるために
数学オンチとして
2つの数の合計を知りたい
scenarios:
-
type: scenario
keyword: 'シナリオ'
title: '2つの数の加算について'
line: 7
steps:
- { keyword_type: 'Given', type: '前提', text: '50 を入力', line: 8 }
- { keyword_type: 'Given', type: 'かつ', text: '70 を入力', line: 9 }
- { keyword_type: 'When', type: 'もし', text: 'add ボタンを押した', line: 10 }
- { keyword_type: 'Then', type: 'ならば', text: '結果は 120 を表示', line: 11 }

View File

@@ -0,0 +1,13 @@
feature:
title: https://rspec.lighthouseapp.com/projects/16211/tickets/246-distorted-console-output-for-slightly-complicated-step-regexp-match
language: en
line: 1
description: ~
scenarios:
-
type: scenario
title: See "No Record(s) Found" for Zero Existing
line: 3
steps:
- { keyword_type: Given, type: Given, text: no public holiday exists in the system, line: 4 }

View File

@@ -0,0 +1,44 @@
feature:
title: multiline
language: en
line: 1
description: ~
background:
line: 3
steps:
- { keyword_type: Given, type: Given, text: passing without a table, line: 4 }
scenarios:
-
type: scenario
title: |-
I'm a multiline name
which goes on and on and on for three lines
yawn
line: 6
steps:
- { keyword_type: Given, type: Given, text: passing without a table, line: 9 }
-
type: outline
title: |-
I'm a multiline name
which goes on and on and on for three lines
yawn
line: 11
steps:
- { keyword_type: Given, type: 'Given', text: '<state> without a table', line: 14 }
examples:
16: [state]
17: [passing]
-
type: outline
title: name
line: 19
steps:
- { keyword_type: Given, type: 'Given', text: '<state> without a table', line: 20 }
examples:
22: [state]
23: [passing]

View File

@@ -0,0 +1,65 @@
feature:
title: multiline
language: en
line: 1
description: |-
Feature description
With etc.
background:
line: 8
steps:
- { keyword_type: Given, type: Given, text: passing without a table, line: 11 }
scenarios:
-
type: scenario
title: |-
I'm a multiline name
which goes on and on and on for three lines
yawn
line: 13
steps:
- { keyword_type: Given, type: Given, text: passing without a table, line: 19 }
-
type: outline
title: |-
I'm a multiline name
which goes on and on and on for three lines
yawn
line: 21
steps:
- { keyword_type: 'Given', type: 'Given', text: '<state> without a table', line: 28 }
examples:
34: [state]
35: [passing]
-
type: outline
title: name
line: 37
steps:
- { keyword_type: 'Given', type: 'Given', text: '<state> without a table', line: 40 }
examples:
45: [state]
46: [passing]
-
type: outline
title: |-
I'm a multiline name
which goes on and on and on for three lines
yawn
line: 48
steps:
- { keyword_type: 'Given', type: 'Given', text: '<state> without a table', line: 55 }
examples:
60: [state]
61: [passing]

View File

@@ -0,0 +1,47 @@
feature:
title: A multiple py string feature
line: 1
language: en
description: ~
scenarios:
-
type: scenario
title: ~
line: 3
steps:
-
keyword_type: When
type: When
text: I enter a string
line: 4
arguments:
-
type: pystring
text: |-
-
a string
with something
be
a
u
ti
ful
-
keyword_type: Then
type: Then
text: String must be
line: 15
arguments:
-
type: pystring
text: |-
-
a string
with something
be
a
u
ti
ful

View File

@@ -0,0 +1,33 @@
feature:
title: Login
language: en
line: 1
description: |-
To ensure the safety of the application
A regular user of the system
Must authenticate before using the app
scenarios:
-
type: outline
title: Failed Login
line: 7
steps:
- { keyword_type: 'Given', type: 'Given', text: 'the user "known_user"', line: 8 }
- { keyword_type: 'When', type: 'When', text: 'I go to the main page', line: 10 }
- { keyword_type: 'Then', type: 'Then', text: 'I should see the login form', line: 11 }
- { keyword_type: 'When', type: 'When', text: 'I fill in "login" with "<login>"', line: 13 }
- { keyword_type: 'When', type: 'And', text: 'I fill in "password" with "<password>"', line: 14 }
- { keyword_type: 'When', type: 'And', text: 'I press "Log In"', line: 15 }
- { keyword_type: 'Then', type: 'Then', text: 'the login request should fail', line: 16 }
- { keyword_type: 'Then', type: 'And', text: 'I should see the error message "Login or Password incorrect"', line: 17 }
examples:
20: [login, password]
21: ['', '']
22: [unknown_user, '']
23: [known_user, '']
24: ['', wrong_password]
25: ['', known_userpass]
26: [unknown_user, wrong_password]
27: [unknown_user, known_userpass]
28: [known_user, wrong_password]

View File

@@ -0,0 +1,29 @@
feature:
title: Unsubstituted argument placeholder
language: en
line: 1
description: ~
scenarios:
-
type: outline
title: 'See Annual Leave Details (as Management & Human Resource)'
line: 3
steps:
-
keyword_type: Given
type: Given
text: the following users exist in the system
line: 4
arguments:
-
type: table
rows:
5: [ name, email, role_assignments, group_memberships ]
6: [ Jane, jane@fmail.com, <role>, Sales (manager) ]
7: [ Max, max@fmail.com, '', Sales (member) ]
8: [ Carol, carol@fmail.com, '', Sales (member) ]
9: [ Cat, cat@fmail.com, '', '' ]
examples:
12: [ role ]
13: [ HUMAN RESOURCE ]

View File

@@ -0,0 +1,22 @@
feature:
title: A py string feature
language: en
line: 1
description: ~
scenarios:
-
type: scenario
title: ~
line: 3
steps:
-
keyword_type: Then
type: Then
text: I should see
line: 4
arguments:
-
type: pystring
swallow: 6
text: "a string with #something"

View File

@@ -0,0 +1,21 @@
feature:
title: Сложение чисел
keyword: Функционал
language: ru
line: 2
description: |-
Чтобы не складывать в уме
Все, у кого с этим туго
Хотят автоматическое сложение целых чисел
scenarios:
-
type: scenario
keyword: Сценарий
title: Сложение двух целых чисел
line: 7
steps:
- { keyword_type: 'Given', type: 'Допустим', text: 'я ввожу число 50', line: 8 }
- { keyword_type: 'Given', type: 'И', text: 'затем ввожу число 70', line: 9 }
- { keyword_type: 'Then', type: 'Если', text: 'я нажимаю "+"', line: 10 }
- { keyword_type: 'When', type: 'То', text: 'результатом должно быть число 120', line: 11 }

View File

@@ -0,0 +1,11 @@
feature:
title: Тест комментов
keyword: Функционал
language: ru
line: 7
description: |-
i18n должен правильно считываться
Даже если в начале файла 1000
комментов!
scenarios: ~

View File

@@ -0,0 +1,34 @@
feature:
title: Последовательные вычисления
keyword: Функционал
language: ru
line: 2
description: |-
Чтобы вычислять сложные выражения
Пользователи хотят проводить вычисления над результатом предыдущей операций
background:
keyword: Предыстория
line: 6
steps:
- { keyword_type: Given, type: Допустим, text: я сложил 3 и 5, line: 7 }
scenarios:
-
type: scenario
keyword: Сценарий
title: сложение с результатом последней операций
line: 9
steps:
- { keyword_type: Then, type: Если, text: 'я ввожу число 4', line: 10 }
- { keyword_type: Then, type: И, text: 'нажимаю "+"', line: 11 }
- { keyword_type: When, type: То, text: 'результатом должно быть число 12', line: 12 }
-
type: scenario
keyword: Сценарий
title: деление результата последней операции
line: 14
steps:
- { keyword_type: Then, type: Если, text: 'я ввожу число 2', line: 15 }
- { keyword_type: Then, type: И, text: 'нажимаю "/"', line: 16 }
- { keyword_type: When, type: То, text: 'результатом должно быть число 4', line: 17 }

View File

@@ -0,0 +1,27 @@
feature:
title: Деление чисел
keyword: Функционал
language: ru
line: 2
description: |-
Поскольку деление сложный процесс и люди часто допускают ошибки
Нужно дать им возможность делить на калькуляторе
scenarios:
-
type: outline
keyword: Структура сценария
title: Целочисленное деление
line: 6
steps:
- { keyword_type: Given, type: 'Допустим', text: 'я ввожу число <делимое>', line: 7 }
- { keyword_type: Given, type: 'И', text: 'затем ввожу число <делитель>', line: 8 }
- { keyword_type: Then, type: 'Если', text: 'я нажимаю "/"', line: 9 }
- { keyword_type: When, type: 'То', text: 'результатом должно быть число <частное>', line: 10 }
examples:
keyword: Значения
13: [делимое, делитель, частное]
14: [100, 2, 50]
15: [28, 7, 4]
16: [0, 5, 0]

View File

@@ -0,0 +1,18 @@
feature:
title: Using the Console Formatter
language: en
line: 3
description: |-
In order to verify this error
I want to run this feature using the progress format
So that it can be fixed
scenarios:
-
type: scenario
title: A normal feature
line: 8
steps:
- { keyword_type: 'Given', type: 'Given', text: 'I have a pending step', line: 9 }
- { keyword_type: 'When', type: 'When', text: 'I run this feature with the progress format', line: 10 }
- { keyword_type: 'Then', type: 'Then', text: "I should get a no method error for 'backtrace_line'", line: 11 }

View File

@@ -0,0 +1,42 @@
feature:
title: A scenario outline
language: en
line: 1
description: ~
scenarios:
-
type: outline
title: ~
line: 3
steps:
- { keyword_type: Given, type: Given, text: I add <a> and <b>, line: 4 }
-
keyword_type: When
type: When
text: I pass a table argument
line: 6
arguments:
-
type: table
rows:
7: [foo, bar]
8: [bar, baz]
- { keyword_type: Then, type: Then, text: I the result should be <c>, line: 10 }
-
keyword_type: Then
type: And
text: the table should be properly escaped:
line: 12
arguments:
-
type: table
rows:
13: ['|a', b, c]
14: [1, '|2', 3]
15: [2, 3, '|4']
examples:
18: [ a, b, c ]
19: [ 1, '|2', 3 ]
20: [ 2, 3, 4 ]

View File

@@ -0,0 +1,35 @@
feature:
title: Tag samples
language: en
tags: [sample_one]
line: 2
description: ~
scenarios:
-
type: scenario
title: Passing
tags: [sample_two, sample_four]
line: 5
steps:
- { keyword_type: 'Given', type: 'Given', text: 'missing', line: 6 }
-
type: outline
title: ~
tags: [sample_three]
line: 9
steps:
- { keyword_type: 'Given', type: 'Given', text: '<state>', line: 10 }
examples:
12: [state]
13: [missing]
-
type: scenario
title: Skipped
tags: [sample_three, sample_four]
line: 16
steps:
- { keyword_type: 'Given', type: 'Given', text: 'missing', line: 17 }

View File

@@ -0,0 +1,18 @@
feature:
title: Test::Unit
language: en
line: 1
description: |-
In order to please people who like Test::Unit
As a Cucumber user
I want to be able to use assert* in my step definitions
scenarios:
-
type: scenario
title: assert_equal
line: 6
steps:
- { keyword_type: 'Given', type: 'Given', text: 'x = 5', line: 7 }
- { keyword_type: 'Given', type: 'And', text: 'y = 5', line: 8 }
- { keyword_type: 'Then', type: 'Then', text: 'I can assert that x == y', line: 9 }

View File

@@ -0,0 +1,29 @@
feature:
title: A py string feature
language: en
line: 1
description: ~
scenarios:
-
type: scenario
title: ~
line: 3
steps:
-
keyword_type: Then
type: Then
text: String must be
line: 4
arguments:
-
type: pystring
text: |-
-
a string
with something
be
a
u
ti
ful

View File

@@ -0,0 +1,38 @@
feature:
title: undefined multiline args
language: en
line: 1
description: ~
scenarios:
-
type: scenario
title: pystring
line: 3
steps:
-
keyword_type: Given
type: Given
text: a pystring
line: 4
arguments:
-
type: pystring
text: ' example'
-
type: scenario
title: table
line: 9
steps:
-
keyword_type: Given
type: Given
text: a table
line: 10
arguments:
-
type: table
rows:
11: [table]
12: [example]

View File

@@ -0,0 +1,17 @@
# language: en
Feature: Addition
In order to avoid silly mistakes
As a math idiot
I want to be told the sum of two numbers
Scenario: Add two numbers
Given I have entered 11 into the calculator
And I have entered 12 into the calculator
When I press add
Then the result should be 23 on the screen
Scenario: Div two numbers
Given I have entered 10 into the calculator
And I have entered 2 into the calculator
When I press div
Then the result should be 5 on the screen

View File

@@ -0,0 +1,7 @@
Feature: Feature with background
Background:
Given a passing step
Scenario:
Given a failing step

View File

@@ -0,0 +1,13 @@
Feature: Feature with titled background
Background: Some Background
title with
couple
of
| continuous |
"""
strings
Given a passing step
Scenario:
Given a failing step

View File

@@ -0,0 +1,26 @@
Feature: Big PyString
Scenario:
Then it should fail with:
"""
# language: ru
UUUUUU
2 scenarios (2 undefined)
6 steps (6 undefined)
You can implement step definitions for undefined steps with these snippets:
$steps->Given('/^I have entered (\d+)$/', function($world, $arg1) {
throw new \Everzet\Behat\Exception\Pending();
});
$steps->Then('/^I must have (\d+)$/', function($world, $arg1) {
throw new \Everzet\Behat\Exception\Pending();
});
$steps->Then('/^String must be \'([^\']*)\'$/', function($world, $arg1) {
throw new \Everzet\Behat\Exception\Pending();
});
"""

View File

@@ -0,0 +1,10 @@
Feature: Feature N4
@normal
Scenario:
Given Some normal step N41
And Some fast step N42
@fast
Scenario:
Given Some slow step N43

View File

@@ -0,0 +1,34 @@
Feature: Fibonacci
In order to calculate super fast fibonacci series
As a pythonista
I want to use Python for that
#
# Background:
# Given passing without a table
#
# Scenario: I'm a multiline name
# which goes on and on and on for three lines
# yawn
# Given passing without a table
#
# Scenario:
# Then I should see
# """
# a string with #something
# """
#
# Scenario Outline: Series
# When I ask python to calculate fibonacci up to <n>
# Then it should give me <series>
#
# Examples:
# | n | series |
# | 1 | [] |
# | 2 | [1, 1] |
# | 3 | [1, 1, 2] |
# | 4 | [1, 1, 2, 3] |
# | 6 | [1, 1, 2, 3, 5] |
# | 9 | [1, 1, 2, 3, 5, 8] |
# | 100 | [1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] |
#

View File

@@ -0,0 +1,32 @@
# Users want to use cucumber, so tests are necessary to verify
# it is all working as expected
Feature: Using the Console Formatter
# com
# comment
#com
In order to verify this error # comment
I want to run this feature using the progress format#comment
# COMMENT
# COMMENT
# COMMENT
# COMMENT
So that it can be fixed
#comment
Scenario: A normal feature #comment in scenario title
#comment
Given I have a pending step #comment
#comment
#comment
When I run this feature with the progress format #comment
#comment
#comment
#comment
Then I should get a no method error for 'backtrace_line'

View File

@@ -0,0 +1,22 @@
# language: en
# multiline
# comment
# YEAH
Feature: Complex descriptions
Some description with
| table | row|
and
"""
"""
Scenario: Some
| complex | description |
"""
hell yeah
"""
Given one two three

View File

@@ -0,0 +1,2 @@
Feature: Some feature
#

View File

@@ -0,0 +1,7 @@
Feature: Cucumber command line
In order to write better software
Developers should be able to execute requirements as tests
Scenario: Pending Scenario at the end of a file with whitespace after it

View File

@@ -0,0 +1,7 @@
Feature: Cucumber command line
In order to write better software
Developers should be able to execute requirements as tests
Scenario: Pending Scenario at the end of a file with whitespace after it
#

View File

@@ -0,0 +1,12 @@
Feature: Math
In order to avoid silly mistakes
As a math idiot
I want to be told the calculation of two numbers
Scenario: Add two numbers
Scenario: Div two numbers
Scenario: Multiply two numbers
Scenario: Sub two numbers

View File

@@ -0,0 +1,19 @@
Feature: Fibonacci
In order to calculate super fast fibonacci series
As a pythonista
I want to use Python for that
Scenario Outline: Series
When I ask python to calculate fibonacci up to <n>
Then it should give me <series>
Examples:
| n | series |
| 1 | [] |
| 2 | [1, 1] |
| 3 | [1, 1, 2] |
| 4 | [1, 1, 2, 3] |
| 6 | [1, 1, 2, 3, 5] |
| 9 | [1, 1, 2, 3, 5, 8] |
| 100 | [1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89] |

View File

@@ -0,0 +1,17 @@
# language: en
Feature: Some '#quoted' string
In order to avoid silly mistakes
As a "#math" idiot
I want to be told the sum of two numbers
Scenario: Add two numbers
Given I have entered 11 into the calculator
And I have entered 12 into the calculator
When I press "#add"
Then the result should be 23 on the screen
Scenario: Div "#two" numbers # as
Given I have entered 10 into the calculator
And I have entered # 2 into the calculator
When I press div
Then the result should be 5 on the screen

View File

@@ -0,0 +1,24 @@
Feature: test pystring
second line
Scenario: testing py string in scenario
second line
Given the pystring is
"""
Test store name
Denmark, Kolding
6000
"""
Scenario Outline: testing py string in scenario outline
second line
Given the pystring is
"""
Test store name
Denmark, Kolding
6000
"""
Examples:
||

View File

@@ -0,0 +1,11 @@
# language: ja
フィーチャ: 加算
2
シナリオ: 2つの数の加算について
前提 50
かつ 70
もし add
ならば 120

View File

@@ -0,0 +1,4 @@
Feature: https://rspec.lighthouseapp.com/projects/16211/tickets/246-distorted-console-output-for-slightly-complicated-step-regexp-match
Scenario: See "No Record(s) Found" for Zero Existing
Given no public holiday exists in the system

View File

@@ -0,0 +1,23 @@
Feature: multiline
Background:
Given passing without a table
Scenario: I'm a multiline name
which goes on and on and on for three lines
yawn
Given passing without a table
Scenario Outline: I'm a multiline name
which goes on and on and on for three lines
yawn
Given <state> without a table
Examples:
| state |
|passing|
Scenario Outline: name
Given <state> without a table
Examples:
| state |
|passing|

View File

@@ -0,0 +1,61 @@
Feature: multiline
Feature description
With etc.
Background:
Given passing without a table
Scenario:
I'm a multiline name
which goes on and on and on for three lines
yawn
Given passing without a table
Scenario Outline: I'm a multiline name
which goes on and on and on for three lines
yawn
Given <state> without a table
Examples:
| state |
|passing|
Scenario Outline: name
Given <state> without a table
Examples:
| state |
|passing|
Scenario Outline:
I'm a multiline name
which goes on and on and on for three lines
yawn
Given <state> without a table
Examples:
| state |
|passing|

View File

@@ -0,0 +1,25 @@
Feature: A multiple py string feature
Scenario:
When I enter a string
"""
-
a string
with something
be
a
u
ti
ful
"""
Then String must be
"""
-
a string
with something
be
a
u
ti
ful
"""

View File

@@ -0,0 +1,28 @@
Feature: Login
To ensure the safety of the application
A regular user of the system
Must authenticate before using the app
Scenario Outline: Failed Login
Given the user "known_user"
When I go to the main page
Then I should see the login form
When I fill in "login" with "<login>"
And I fill in "password" with "<password>"
And I press "Log In"
Then the login request should fail
And I should see the error message "Login or Password incorrect"
Examples:
| login | password |
| | |
| unknown_user | |
| known_user | |
| | wrong_password |
| | known_userpass |
| unknown_user | wrong_password |
| unknown_user | known_userpass |
| known_user | wrong_password |

View File

@@ -0,0 +1,13 @@
Feature: Unsubstituted argument placeholder
Scenario Outline: See Annual Leave Details (as Management & Human Resource)
Given the following users exist in the system
| name | email | role_assignments | group_memberships |
| Jane | jane@fmail.com | <role> | Sales (manager) |
| Max | max@fmail.com | | Sales (member) |
| Carol | carol@fmail.com | | Sales (member) |
| Cat | cat@fmail.com | | |
Examples:
| role |
| HUMAN RESOURCE |

View File

@@ -0,0 +1,8 @@
Feature: A py string feature
Scenario:
Then I should see
"""
a string with #something
"""

View File

@@ -0,0 +1,11 @@
# language: ru
Функционал: Сложение чисел
Чтобы не складывать в уме
Все, у кого с этим туго
Хотят автоматическое сложение целых чисел
Сценарий: Сложение двух целых чисел
Допустим я ввожу число 50
И затем ввожу число 70
Если я нажимаю "+"
То результатом должно быть число 120

View File

@@ -0,0 +1,10 @@
# Comments
# comments
# COOOOOMMEEEENTS
#
# language: ru
Функционал: Тест комментов
i18n должен правильно считываться
Даже если в начале файла 1000
комментов!

View File

@@ -0,0 +1,17 @@
# language: ru
Функционал: Последовательные вычисления
Чтобы вычислять сложные выражения
Пользователи хотят проводить вычисления над результатом предыдущей операций
Предыстория:
Допустим я сложил 3 и 5
Сценарий: сложение с результатом последней операций
Если я ввожу число 4
И нажимаю "+"
То результатом должно быть число 12
Сценарий: деление результата последней операции
Если я ввожу число 2
И нажимаю "/"
То результатом должно быть число 4

View File

@@ -0,0 +1,16 @@
# language: ru
Функционал: Деление чисел
Поскольку деление сложный процесс и люди часто допускают ошибки
Нужно дать им возможность делить на калькуляторе
Структура сценария: Целочисленное деление
Допустим я ввожу число <делимое>
И затем ввожу число <делитель>
Если я нажимаю "/"
То результатом должно быть число <частное>
Значения:
| делимое | делитель | частное |
| 100 | 2 | 50 |
| 28 | 7 | 4 |
| 0 | 5 | 0 |

View File

@@ -0,0 +1,12 @@
# Users want to use cucumber, so tests are necessary to verify
# it is all working as expected
Feature: Using the Console Formatter
In order to verify this error
I want to run this feature using the progress format
So that it can be fixed
Scenario: A normal feature
Given I have a pending step
When I run this feature with the progress format
Then I should get a no method error for 'backtrace_line'

View File

@@ -0,0 +1,20 @@
Feature: A scenario outline
# COMMENT
Scenario Outline:
Given I add <a> and <b>
# comment
When I pass a table argument
| foo | bar |
| bar | baz |
#comment
Then I the result should be <c>
# comment
And the table should be properly escaped:
| \|a | b | c |
| 1 | \|2 | 3 |
| 2 | 3 | \|4 |
#comment
Examples:
| a | b | c |
| 1 | \|2 | 3 |
| 2 | 3 | 4 |

View File

@@ -0,0 +1,17 @@
@sample_one
Feature: Tag samples
@sample_two @sample_four
Scenario: Passing
Given missing
@sample_three
Scenario Outline:
Given <state>
Examples:
|state|
|missing|
@sample_three @sample_four
Scenario: Skipped
Given missing

View File

@@ -0,0 +1,9 @@
Feature: Test::Unit
In order to please people who like Test::Unit
As a Cucumber user
I want to be able to use assert* in my step definitions
Scenario: assert_equal
Given x = 5
And y = 5
Then I can assert that x == y

View File

@@ -0,0 +1,14 @@
Feature: A py string feature
Scenario:
Then String must be
"""
-
a string
with something
be
a
u
ti
ful
"""

View File

@@ -0,0 +1,12 @@
Feature: undefined multiline args
Scenario: pystring
Given a pystring
"""
example
"""
Scenario: table
Given a table
| table |
|example|

View File

@@ -0,0 +1,606 @@
#
# !!! DON'T TOUCH THIS FILE, IT WAS AUTODOWNLOADED FROM:
# https://github.com/cucumber/gherkin/blob/master/lib/gherkin/i18n.yml
#
# encoding: UTF-8
#
# We use ISO 639-1 (language) and ISO 3166 alpha-2 (region - if applicable):
# http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
# http://en.wikipedia.org/wiki/ISO_3166-1
#
# If you want several aliases for a keyword, just separate them
# with a | character. The * is a step keyword alias for all translations.
#
# If you do *not* want a trailing space after a keyword, end it with a < character.
# (See Chinese for examples).
#
"en":
name: English
native: English
feature: Feature
background: Background
scenario: Scenario
scenario_outline: Scenario Outline|Scenario Template
examples: Examples|Scenarios
given: "*|Given"
when: "*|When"
then: "*|Then"
and: "*|And"
but: "*|But"
# Please keep the grammars in alphabetical order by name from here and down.
"ar":
name: Arabic
native: العربية
feature: خاصية
background: الخلفية
scenario: سيناريو
scenario_outline: سيناريو مخطط
examples: امثلة
given: "*|بفرض"
when: "*|متى|عندما"
then: "*|اذاً|ثم"
and: "*|و"
but: "*|لكن"
"bg":
name: Bulgarian
native: български
feature: Функционалност
background: Предистория
scenario: Сценарий
scenario_outline: Рамка на сценарий
examples: Примери
given: "*|Дадено"
when: "*|Когато"
then: "*|То"
and: "*|И"
but: "*|Но"
"ca":
name: Catalan
native: català
background: Rerefons|Antecedents
feature: Característica|Funcionalitat
scenario: Escenari
scenario_outline: Esquema de l'escenari
examples: Exemples
given: "*|Donat|Donada|Atès|Atesa"
when: "*|Quan"
then: "*|Aleshores|Cal"
and: "*|I"
but: "*|Però"
"cy-GB":
name: Welsh
native: Cymraeg
background: Cefndir
feature: Arwedd
scenario: Scenario
scenario_outline: Scenario Amlinellol
examples: Enghreifftiau
given: "*|Anrhegedig a"
when: "*|Pryd"
then: "*|Yna"
and: "*|A"
but: "*|Ond"
"cs":
name: Czech
native: Česky
feature: Požadavek
background: Pozadí|Kontext
scenario: Scénář
scenario_outline: Náčrt Scénáře|Osnova scénáře
examples: Příklady
given: "*|Pokud"
when: "*|Když"
then: "*|Pak"
and: "*|A také|A"
but: "*|Ale"
"da":
name: Danish
native: dansk
feature: Egenskab
background: Baggrund
scenario: Scenarie
scenario_outline: Abstrakt Scenario
examples: Eksempler
given: "*|Givet"
when: "*|Når"
then: "*|Så"
and: "*|Og"
but: "*|Men"
"de":
name: German
native: Deutsch
feature: Funktionalität
background: Grundlage
scenario: Szenario
scenario_outline: Szenariogrundriss
examples: Beispiele
given: "*|Angenommen|Gegeben sei"
when: "*|Wenn"
then: "*|Dann"
and: "*|Und"
but: "*|Aber"
"en-au":
name: Australian
native: Australian
feature: Crikey
background: Background
scenario: Mate
scenario_outline: Blokes
examples: Cobber
given: "*|Ya know how"
when: "*|When"
then: "*|Ya gotta"
and: "*|N"
but: "*|Cept"
"en-lol":
name: LOLCAT
native: LOLCAT
feature: OH HAI
background: B4
scenario: MISHUN
scenario_outline: MISHUN SRSLY
examples: EXAMPLZ
given: "*|I CAN HAZ"
when: "*|WEN"
then: "*|DEN"
and: "*|AN"
but: "*|BUT"
"en-pirate":
name: Pirate
native: Pirate
feature: Ahoy matey!
background: Yo-ho-ho
scenario: Heave to
scenario_outline: Shiver me timbers
examples: Dead men tell no tales
given: "*|Gangway!"
when: "*|Blimey!"
then: "*|Let go and haul"
and: "*|Aye"
but: "*|Avast!"
"en-Scouse":
name: Scouse
native: Scouse
feature: Feature
background: "Dis is what went down"
scenario: "The thing of it is"
scenario_outline: "Wharrimean is"
examples: Examples
given: "*|Givun|Youse know when youse got"
when: "*|Wun|Youse know like when"
then: "*|Dun|Den youse gotta"
and: "*|An"
but: "*|Buh"
"en-tx":
name: Texan
native: Texan
feature: Feature
background: Background
scenario: Scenario
scenario_outline: All y'all
examples: Examples
given: "*|Given y'all"
when: "*|When y'all"
then: "*|Then y'all"
and: "*|And y'all"
but: "*|But y'all"
"eo":
name: Esperanto
native: Esperanto
feature: Trajto
background: Fono
scenario: Scenaro
scenario_outline: Konturo de la scenaro
examples: Ekzemploj
given: "*|Donitaĵo"
when: "*|Se"
then: "*|Do"
and: "*|Kaj"
but: "*|Sed"
"es":
name: Spanish
native: español
background: Antecedentes
feature: Característica
scenario: Escenario
scenario_outline: Esquema del escenario
examples: Ejemplos
given: "*|Dado|Dada|Dados|Dadas"
when: "*|Cuando"
then: "*|Entonces"
and: "*|Y"
but: "*|Pero"
"et":
name: Estonian
native: eesti keel
feature: Omadus
background: Taust
scenario: Stsenaarium
scenario_outline: Raamstsenaarium
examples: Juhtumid
given: "*|Eeldades"
when: "*|Kui"
then: "*|Siis"
and: "*|Ja"
but: "*|Kuid"
"fi":
name: Finnish
native: suomi
feature: Ominaisuus
background: Tausta
scenario: Tapaus
scenario_outline: Tapausaihio
examples: Tapaukset
given: "*|Oletetaan"
when: "*|Kun"
then: "*|Niin"
and: "*|Ja"
but: "*|Mutta"
"fr":
name: French
native: français
feature: Fonctionnalité
background: Contexte
scenario: Scénario
scenario_outline: Plan du scénario|Plan du Scénario
examples: Exemples
given: "*|Soit|Etant donné|Etant donnée|Etant donnés|Etant données|Étant donné|Étant donnée|Étant donnés|Étant données"
when: "*|Quand|Lorsque|Lorsqu'<"
then: "*|Alors"
and: "*|Et"
but: "*|Mais"
"he":
name: Hebrew
native: עברית
feature: תכונה
background: רקע
scenario: תרחיש
scenario_outline: תבנית תרחיש
examples: דוגמאות
given: "*|בהינתן"
when: "*|כאשר"
then: "*|אז|אזי"
and: "*|וגם"
but: "*|אבל"
"hr":
name: Croatian
native: hrvatski
feature: Osobina|Mogućnost|Mogucnost
background: Pozadina
scenario: Scenarij
scenario_outline: Skica|Koncept
examples: Primjeri|Scenariji
given: "*|Zadan|Zadani|Zadano"
when: "*|Kada|Kad"
then: "*|Onda"
and: "*|I"
but: "*|Ali"
"hu":
name: Hungarian
native: magyar
feature: Jellemző
background: Háttér
scenario: Forgatókönyv
scenario_outline: Forgatókönyv vázlat
examples: Példák
given: "*|Amennyiben|Adott"
when: "*|Majd|Ha|Amikor"
then: "*|Akkor"
and: "*|És"
but: "*|De"
"id":
name: Indonesian
native: Bahasa Indonesia
feature: Fitur
background: Dasar
scenario: Skenario
scenario_outline: Skenario konsep
examples: Contoh
given: "*|Dengan"
when: "*|Ketika"
then: "*|Maka"
and: "*|Dan"
but: "*|Tapi"
"is":
name: Icelandic
native: Íslenska
feature: Eiginleiki
background: Bakgrunnur
scenario: Atburðarás
scenario_outline: Lýsing Atburðarásar|Lýsing Dæma
examples: Dæmi|Atburðarásir
given: "*|Ef"
when: "*|Þegar"
then: "*|Þá"
and: "*|Og"
but: "*|En"
"it":
name: Italian
native: italiano
feature: Funzionalità
background: Contesto
scenario: Scenario
scenario_outline: Schema dello scenario
examples: Esempi
given: "*|Dato|Data|Dati|Date"
when: "*|Quando"
then: "*|Allora"
and: "*|E"
but: "*|Ma"
"ja":
name: Japanese
native: 日本語
feature: フィーチャ|機能
background: 背景
scenario: シナリオ
scenario_outline: シナリオアウトライン|シナリオテンプレート|テンプレ|シナリオテンプレ
examples: 例|サンプル
given: "*|前提<"
when: "*|もし<"
then: "*|ならば<"
and: "*|かつ<"
but: "*|しかし<|但し<|ただし<"
"ko":
name: Korean
native: 한국어
background: 배경
feature: 기능
scenario: 시나리오
scenario_outline: 시나리오 개요
examples:
given: "*|조건<|먼저<"
when: "*|만일<|만약<"
then: "*|그러면<"
and: "*|그리고<"
but: "*|하지만<|단<"
"lt":
name: Lithuanian
native: lietuvių kalba
feature: Savybė
background: Kontekstas
scenario: Scenarijus
scenario_outline: Scenarijaus šablonas
examples: Pavyzdžiai|Scenarijai|Variantai
given: "*|Duota"
when: "*|Kai"
then: "*|Tada"
and: "*|Ir"
but: "*|Bet"
"lu":
name: Luxemburgish
native: Lëtzebuergesch
feature: Funktionalitéit
background: Hannergrond
scenario: Szenario
scenario_outline: Plang vum Szenario
examples: Beispiller
given: "*|ugeholl"
when: "*|wann"
then: "*|dann"
and: "*|an|a"
but: "*|awer|mä"
"lv":
name: Latvian
native: latviešu
feature: Funkcionalitāte|Fīča
background: Konteksts|Situācija
scenario: Scenārijs
scenario_outline: Scenārijs pēc parauga
examples: Piemēri|Paraugs
given: "*|Kad"
when: "*|Ja"
then: "*|Tad"
and: "*|Un"
but: "*|Bet"
"nl":
name: Dutch
native: Nederlands
feature: Functionaliteit
background: Achtergrond
scenario: Scenario
scenario_outline: Abstract Scenario
examples: Voorbeelden
given: "*|Gegeven|Stel"
when: "*|Als"
then: "*|Dan"
and: "*|En"
but: "*|Maar"
"no":
name: Norwegian
native: norsk
feature: Egenskap
background: Bakgrunn
scenario: Scenario
scenario_outline: Scenariomal|Abstrakt Scenario
examples: Eksempler
given: "*|Gitt"
when: "*|Når"
then: "*|Så"
and: "*|Og"
but: "*|Men"
"pl":
name: Polish
native: polski
feature: Właściwość
background: Założenia
scenario: Scenariusz
scenario_outline: Szablon scenariusza
examples: Przykłady
given: "*|Zakładając|Mając"
when: "*|Jeżeli|Jeśli"
then: "*|Wtedy"
and: "*|Oraz|I"
but: "*|Ale"
"pt":
name: Portuguese
native: português
background: Contexto
feature: Funcionalidade
scenario: Cenário|Cenario
scenario_outline: Esquema do Cenário|Esquema do Cenario
examples: Exemplos
given: "*|Dado|Dada|Dados|Dadas"
when: "*|Quando"
then: "*|Então|Entao"
and: "*|E"
but: "*|Mas"
"ro":
name: Romanian
native: română
background: Context
feature: Functionalitate|Funcționalitate|Funcţionalitate
scenario: Scenariu
scenario_outline: Structura scenariu|Structură scenariu
examples: Exemple
given: "*|Date fiind|Dat fiind|Dati fiind|Dați fiind|Daţi fiind"
when: "*|Cand|Când"
then: "*|Atunci"
and: "*|Si|Și|Şi"
but: "*|Dar"
"ru":
name: Russian
native: русский
feature: Функция|Функционал|Свойство
background: Предыстория|Контекст
scenario: Сценарий
scenario_outline: Структура сценария
examples: Примеры
given: "*|Допустим|Дано|Пусть"
when: "*|Если|Когда"
then: "*|То|Тогда"
and: "*|И|К тому же"
but: "*|Но|А"
"sv":
name: Swedish
native: Svenska
feature: Egenskap
background: Bakgrund
scenario: Scenario
scenario_outline: Abstrakt Scenario|Scenariomall
examples: Exempel
given: "*|Givet"
when: "*|När"
then: "*|Så"
and: "*|Och"
but: "*|Men"
"sk":
name: Slovak
native: Slovensky
feature: Požiadavka
background: Pozadie
scenario: Scenár
scenario_outline: Náčrt Scenáru
examples: Príklady
given: "*|Pokiaľ"
when: "*|Keď"
then: "*|Tak"
and: "*|A"
but: "*|Ale"
"sr-Latn":
name: Serbian (Latin)
native: Srpski (Latinica)
feature: Funkcionalnost|Mogućnost|Mogucnost|Osobina
background: Kontekst|Osnova|Pozadina
scenario: Scenario|Primer
scenario_outline: Struktura scenarija|Skica|Koncept
examples: Primeri|Scenariji
given: "*|Zadato|Zadate|Zatati"
when: "*|Kada|Kad"
then: "*|Onda"
and: "*|I"
but: "*|Ali"
"sr-Cyrl":
name: Serbian
native: Српски
feature: Функционалност|Могућност|Особина
background: Контекст|Основа|Позадина
scenario: Сценарио|Пример
scenario_outline: Структура сценарија|Скица|Концепт
examples: Примери|Сценарији
given: "*|Задато|Задате|Задати"
when: "*|Када|Кад"
then: "*|Онда"
and: "*|И"
but: "*|Али"
"tr":
name: Turkish
native: Türkçe
feature: Özellik
background: Geçmiş
scenario: Senaryo
scenario_outline: Senaryo taslağı
examples: Örnekler
given: "*|Diyelim ki"
when: "*|Eğer ki"
then: "*|O zaman"
and: "*|Ve"
but: "*|Fakat|Ama"
"uk":
name: Ukrainian
native: Українська
feature: Функціонал
background: Передумова
scenario: Сценарій
scenario_outline: Структура сценарію
examples: Приклади
given: "*|Припустимо|Припустимо, що|Нехай|Дано"
when: "*|Якщо|Коли"
then: "*|То|Тоді"
and: "*|І|А також|Та"
but: "*|Але"
"uz":
name: Uzbek
native: Узбекча
feature: Функционал
background: Тарих
scenario: Сценарий
scenario_outline: Сценарий структураси
examples: Мисоллар
given: "*|Агар"
when: "*|Агар"
then: "*|Унда"
and: "*|Ва"
but: "*|Лекин|Бирок|Аммо"
"vi":
name: Vietnamese
native: Tiếng Việt
feature: Tính năng
background: Bối cảnh
scenario: Tình huống|Kịch bản
scenario_outline: Khung tình huống|Khung kịch bản
examples: Dữ liệu
given: "*|Biết|Cho"
when: "*|Khi"
then: "*|Thì"
and: "*|Và"
but: "*|Nhưng"
"zh-CN":
name: Chinese simplified
native: 简体中文
feature: 功能
background: 背景
scenario: 场景
scenario_outline: 场景大纲
examples: 例子
given: "*|假如<"
when: "*|当<"
then: "*|那么<"
and: "*|而且<"
but: "*|但是<"
"zh-TW":
name: Chinese traditional
native: 繁體中文
feature: 功能
background: 背景
scenario: 場景|劇本
scenario_outline: 場景大綱|劇本大綱
examples: 例子
given: "*|假設<"
when: "*|當<"
then: "*|那麼<"
and: "*|而且<|並且<"
but: "*|但是<"