OpenLiberty / OpenLiberty/liberty-tools-eclipse
Ensure that test reports are viewable for tests executed against multi-module Maven projects
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 16
- Forks
- 20
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 16
Description
The biggest gap at the moment is in the case where you select the aggregator module on the dashboard and do the sequence:
1."Start"
2."Run tests"
3. "View integration test report" (same w/ UT)
Running the tests works fine, dev mode will go to each sub-module and execute tests. But the viewing of the test report won't find anything.
FWIW, in Liberty Tools Eclipse, if the submodule with the tests are present in the dashboard you could view the test report by selecting the view test report from the sub module.
The design needs to be worked out in more detail but we have to mediate the difference here btw. the view and execution at the aggregate level and the report existing at a submodule level.
FURTHER THOUGHTS
- We could possibly go further and allow execution of tests ONLY scoped to a sub-module. This could be worth doing in this issue, or we could break this out into a follow-up item.
- Somewhat related, we don't handle non-default reporting config https://github.com/OpenLiberty/liberty-tools-eclipse/issues/67
CONTEXT
- ci.maven issue ](https://github.com/OpenLiberty/ci.maven/issues/1721)
- low priority - https://github.com/OpenLiberty/ci.maven/issues/1524
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the dashboard sequence by selecting an aggregator module, starting it, running tests, and opening the integration or unit test report. Review the related ci.maven issues and decide how aggregate-level execution should locate reports stored in submodules; done means those reports are viewable, with any submodule-only execution scope explicitly defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- developer-experience, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100