Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Reporter doesn't run after testing
See original GitHub issueHello,
I run my cucumber with a simple mvn test, but this does not trigger the reporting with cluecumber (using the plugin config found on the README). Is there a way to get it to run after the test command? I can run the reporter just fine with mvn cluecumber-report:reporting
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (3 by maintainers)
Top Results From Across the Web
Test report doesn't appear in expected place in GitHub UI #67
The test report is not attached to each of the run.
Read more >org.mockito.exceptions.Reporter when run test - Stack Overflow
You should use PowerMock 1.7.0RC2 (or 1.7.0RC3 if 1.7.0RC2 doesn't work), and also use powermock-api-mockito2 instead of powermock-api-mockito.
Read more >Test Coverage Troubleshooting Tips - Code Climate
Check out the sample/working test config files on the test reporter GitHub project here. Ask a question and open an issue on the...
Read more >Using reporters - utPLSQL-framework
It provides a human readable test results. To invoke tests with documentation reporter use one of following calls from sql console (SQLPlus). exec...
Read more >Running unit tests in GitHub Actions - Octopus Deploy
After some trial and error, I settled on the test-reporter action, which is demonstrated in this post. Unit testing in Java. The workflow...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It depends on what you want to achieve. We need the enforcer rule since we have multiple test runs (including reruns) that generate multiple results. So we need a special rule to determine when a test fails in case some are rerun.
verifyincludes integration tests which use Failsafe. So it is implicitly included.