feat: add the ability to instantiate GreenMail per-class in addition to per-method #332
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.
I had a use case where I needed GreenMail to be instantiated once per test class instead of once per test method. This behaviour was added to the JUnit5
GreenMailExtension
. Of course, this change is made backwards compatible so it doesn't affect existing code. The corresponding test classcom.icegreen.greenmail.junit5.AlternateLifecyclesTests
shows how the lifecycle can be switched, essentially:The extension works very well, please consider publishing the JUnit5 module to Maven Central.