ASSERT-KTH / ASSERT-KTH/flacoco
Test methods escape execution
- Dominant language
- Java
- Stars
- 38
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
When running flacoco on the `java-maven-junit-helloworld` example from https://github.com/SpoonLabs/astor/tree/master/examples/java-maven-junit-helloworld, not all identified tests are executed.
```
[1950] WARN CoverageRunner - Test TestMethod=com.example.javamavenjunithelloworld.HelloAppTest#classInstanceForCodeCoverageTest result was not reported by test-runner.
[1950] WARN CoverageRunner - Test TestMethod=com.example.javamavenjunithelloworld.HelloAppTest#testBogusArgument result was not reported by test-runner.
[1950] WARN CoverageRunner - Test TestMethod=com.example.javamavenjunithelloworld.HelloAppTest#testDefaultArgument result was not reported by test-runner.
[1950] WARN CoverageRunner - Test TestMethod=com.example.javamavenjunithelloworld.HelloAppTest#testMain result was not reported by test-runner.
[1950] WARN CoverageRunner - Test TestMethod=com.example.javamavenjunithelloworld.HelloAppTest#testTooHighArgument result was not reported by test-runner.
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue by running flacoco on the java-maven-junit-helloworld example linked in the report and inspect the CoverageRunner warnings for the five HelloAppTest methods. Done means all identified test methods are executed and their results are reported by the test runner.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100