3
86%
master: 86%

Ran 20 Feb 2020 01:37PM UTC

Files 356

Run time 48s

Badge

Embed ▾

Committed 20 Feb 2020 01:30PM UTC coverage: 83.02% (+0.02%) from 82.997%

Job # COVERAGE=true

Build Type

push

travis-ci

Committed by

web-flow

Commit Message

[JUnit Platform] Support skipping scenarios with cucumber.filter.tags (#1899)

The JUnit Platform supports skipping tests. For example in JUnit Jupiter a
test can be annotated with `@Disabled`. This test will be marked as skipped.

Cucumber scenarios do not have annotations nor is there any support to disable
specific scenarios. A typical work around with Cucumber JUnit 4 integration was
to set a permanent tag filter for `not @Disabled` in `@CucumberOptions`.

This wasn't possible with the JUnit Platform yet. By adding the
`cucumber.filter.tags` property it becomes possible to recreate JUnit Jupiter's
`@Disabled` functionality.
By setting `cucumber.filter.tags=not @Disabled` property any scenarios tagged
with `@Disabled` will be skipped.

Note that contrary to JUnit 4 skipped scenarios are not removed from the test
hierarchy. This is entirely intentional and a result of the way the JUnit
Platform supports skipping tests.

Run Details

6351 of 7650 relevant lines covered (83.02%)

0.83 hits per line

cucumber / cucumber-jvm / 3824 / 3
86%
master: 86%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 3824.3 (COVERAGE=true)

cucumber / cucumber-jvm / 3824 / 3 86% master: 86%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 3824.3 (COVERAGE=true)

cucumber / cucumber-jvm / 3824 / 3
86%
master: 86%

README BADGES
x