cucumber / cucumber-jvm / 4464
87%
master: 86%

LAST BUILD BRANCH: main
DEFAULT BRANCH: master
Ran
Jobs 1
Files 403
Run time 44s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
4464

push

travis-ci

mpkorstanje 
Merge branch '2102-fix-dry-run' into main

Given a scenario with several steps:

```feature
Scenario:
 Given a passed step
 And a skipped step
 And an pending step
 And an undefined step
 And an ambiguous step
```

When executing this the outcome of the result is:

```
a passed step -> PASSED
a skipped step -> SKIPPED
an pending step -> PENDING
an undefined step -> SKIPPED
an ambiguous step -> AMBIGUOUS
```

This is wrong, because after the first non-passed result all
other steps should be skipped. So:

```
a passed step -> PASSED
a skipped step -> SKIPPED
an pending step -> SKIPPED
an undefined step -> SKIPPED
an ambiguous step -> SKIPPED
```

When using executing this scenario with `--dry-run` the
result is:

```
a passed step -> PASSED
a skipped step -> PASSED
an pending step -> PASSED
an undefined step -> UNDEFINED
an ambiguous step -> AMBIGUOUS
```

And surprisingly enough this is also wrong. While the skipped
and pending states can only be detected by executing an implemented
step, the undefined step should be marked as undefined and the
ambiguous step that follows it should be skipped.

```
a passed step -> PASSED
a skipped step -> PASSED
an pending step -> PASSED
an undefined step -> UNDEFINED
an ambiguous step -> SKIPPED
```

The cause for this confusion lies in the fact that `--dry-run` was
implemented using the skip mechanism rather then its own execution
mode that is distinct from both a regular run and skip mode. By
implementing these as individual execution modes we can avoid this
confusion.

Implementing this however revealed that our formatters were often
being tested with completely undefined scenarios. This does not
provide a representative test and allowed #2102 to come into
existence. Fixing this was rather complicated, the formatters were
being tested with an overly complicated mock implementation.
Replacing this mock implementation with stubs made the tests more
readable and removed a significant chunk of complexity.

Fixes: http... (continued)

7151 of 8269 relevant lines covered (86.48%)

0.86 hits per line

Jobs
ID Job ID Ran Files Coverage
3 4464.3 (COVERAGE=true) 0
86.48
 Travis Job 4464.3
Source Files on build 4464
Detailed source file information is not available for this build.