-
Notifications
You must be signed in to change notification settings - Fork 2
/
run_examples.feature
39 lines (34 loc) · 1.5 KB
/
run_examples.feature
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
Ability: run examples
Examples are the building blocks for describing the application under test.
Running examples means that Senfgurke will try to find and execute a
matching function for each step in an example (aka step implementation).
The result of the executed step will tell you if the application works as
expected (see feature "run steps" for more).
Rule: steps follwing a step with a status other than "OK" should return "SKIPPED" or "MISSING"
Example: example with failed step
Given an example with matching step implementations
"""
Ability: sample feature
Example: sample example
Given a valid step
And an invalid step
And a valid step
And a valid step
"""
When the example is executed
Then step statistics is "4 steps (1 passed, 1 failed, 2 skipped)"
Example: example with pending step
Given an example with matching step implementations
"""
Ability: sample feature
Example: sample example
Given a valid step
And a pending step
And a valid step
And a valid step
"""
When the example is executed
Then step statistics is "4 steps (1 passed, 1 pending, 2 skipped)"
#TODO: add example for missing steps
# to detect missing steps, steps have to be executed even when they are skipped
#TODO: add rule not to show err msg for skipped steps