Introduce CtrfListener feature #75
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alexshamrai
force-pushed
the
feature/investigate-listener
branch
18 times, most recently
from
bfb8d5e to
9dc92b3
Compare
Introduce CtrfListener as an alternative to CtrfExtension for generating CTRF reports, providing flexibility in how users integrate the library. Both implementations now delegate to a shared CtrfReportManager singleton, eliminating code duplication and ensuring consistent behavior. BREAKING CHANGES: - TestProcessor.createTest() now accepts displayName as a parameter instead of ExtensionContext, making it framework-agnostic - TestDetails model enhanced with uniqueId and displayName fields Changes: - Add CtrfListener implementing JUnit Platform TestExecutionListener - Extract shared logic into CtrfReportManager singleton pattern - Refactor CtrfExtension to delegate to CtrfReportManager - Make TestProcessor framework-agnostic for reusability - Reorganize integration tests into three modules: * integration-ctrf-validator: validates generated CTRF reports * integration-tests-extension: tests Extension-based reporting * integration-tests-listener: tests Listener-based reporting - Add separate CI workflows for Extension and Listener integration tests - Update documentation to reflect new architecture This change enables users to choose between @ExtendWith annotation (Extension) or service provider configuration (Listener) based on their project needs, while maintaining a single, well-tested core implementation.
alexshamrai
force-pushed
the
feature/investigate-listener
branch
from
5a8a4cb to
506587d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.