feat: test post-processors #1589
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds a concept of
TestPostProcessorinstances; such instances are suspending consumers ofTestRunResults after a test run, and are loaded via aTestPostProcessorFactorytype which is mapped in through SPI.The first two
TestPostProcessorimplementations will likely be coverage (#1484) and test reporting (#1483).Additionally, test result types (i.e.
TestResultandTestRunResult, etc.), have been decoupled from polyglot types and moved fromgraalvmandbuildertotooling, where they can be used for things like IDE integration. This refactor is precursor work for our JVM runner compat stuff.Changelog