Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trace test execution directories in the remote maven execution #1700

Draft
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

laeubi
Copy link
Member

@laeubi laeubi commented Feb 26, 2024

Currently running tests in maven via m2e is possible but not very convenient as one still needs to navigate to the results then open the correct file. Another pitfall is that even if one has opened the file once, the "classic" JUnit view not update the view even when the file changes afterwards.

This now adds a new process tracking of test executions directories that then can be watched on the m2e side and display the new advanced JUnit view when the run has finished.

@laeubi laeubi marked this pull request as draft February 26, 2024 12:27
Copy link

github-actions bot commented Feb 26, 2024

Test Results

0 files   - 107  0 suites   - 107   0s ⏱️ - 10m 11s
0 tests  - 665  0 ✅  - 655  0 💤  - 10  0 ❌ ±0 
0 runs   - 665  0 ✅  - 654  0 💤  - 11  0 ❌ ±0 

Results for commit d3deebc. ± Comparison against base commit 8789e4c.

♻️ This comment has been updated with latest results.

Currently running tests in maven via m2e is possible but not very
convenient as one still needs to navigate to the results then open the
correct file. Another pitfall is that even if one has opened the file
once, the "classic" JUnit view not update the view even when the file
changes afterwards.

This now adds a new process tracking of test executions directories that
then can be watched on the m2e side and display the new advanced JUnit
view when the run has finished.
@laeubi
Copy link
Member Author

laeubi commented Feb 28, 2024

This is how it currently looks like and serves as a first POC

Peek.2024-02-28.06-07.mp4

to make it really cool / convenient a bit more work needs to be done:

  • The eclipse test results view has some concurrency issues and if m2e is "too fast" can have some UI glitches, one can see this in the video where full the results are only show after selecting "Expand all"
  • The View currently does not support a concept of "projects" so we fake them by adding each project as a test-suite, it would be good to enhance this by the concept of projects/groups so it is more clear what belongs where.
  • Reading files after the run works but is not really dynamic and might better watch the directory
  • Even better it would be to impose an API at plexus-build-api that allows m2e to intercept the process execution and install a test execution listener, then one would get real run time information, see this PR
    Add support for a process API codehaus-plexus/plexus-build-api#79
  • Mojos (e.g. Tycho, surefire and bnd-testing, maybe more) need to be enhanced to use that API

Overall it looks like a quite cool feature to explore, so if anyone is interested in sponsoring further development or working on some of the mentioned points please let me know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant