467
94%

Ran 01 May 2018 03:23PM UTC

Jobs 1

Files 29

Run time 2s

Badge

Embed ▾

pending completion

Build # 467

Build Type

push

travis-ci

Committed by

jhalterman

Commit Message

Add issues tests to `mvn test`. (#132)

I was quite surprised to find that my failing test in https://github.com/jhalterman/failsafe/pull/131 passed `mvn test` during CI. Turns out that the tests in `src/test/java/**/issues/` aren't run because their names don't end with `*Test.java`.

Per http://maven.apache.org/surefire/maven-surefire-plugin/examples/inclusion-exclusion.html:

> By default, the Surefire Plugin will automatically include all test classes with the following wildcard patterns:
>
> * `"**/Test*.java"` - includes all of its subdirectories and all Java filenames that start with "Test".
> * `"**/*Test.java"` - includes all of its subdirectories and all Java filenames that end with "Test".
> * `"**/*Tests.java"` - includes all of its subdirectories and all Java filenames that end with "Tests".
> * `"**/*TestCase.java"` - includes all of its subdirectories and all Java filenames that end with "TestCase".

We could configure them to be run with regex, but it seems easier to just rename them to fit the convention. Convention over configuration, right?

Coverage Stats

1018 of 1168 relevant lines covered (87.16%)

0.87 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	467.1	01 May 2018 03:23PM UTC	0	87.16	Travis Job 467.1

Source Files on build 467

Detailed source file information is not available for this build.

jhalterman / failsafe / 467
94%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 467

jhalterman / failsafe / 467 94%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 467

jhalterman / failsafe / 467
94%

README BADGES
x