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

Remove ExtensionPoint, ExtensionRegistrar, Position etc. and simplify implementation of JUnit 5 TestEngine #232

Closed
marcphilipp opened this issue Apr 29, 2016 · 4 comments

Comments

@marcphilipp
Copy link
Member

No description provided.

@sbrannen
Copy link
Member

in progress

sbrannen added a commit to sbrannen/junit5 that referenced this issue May 2, 2016
sbrannen added a commit to sbrannen/junit5 that referenced this issue May 2, 2016
sbrannen added a commit to sbrannen/junit5 that referenced this issue May 2, 2016
sbrannen added a commit to sbrannen/junit5 that referenced this issue May 2, 2016
sbrannen added a commit to sbrannen/junit5 that referenced this issue May 2, 2016
sbrannen added a commit to sbrannen/junit5 that referenced this issue May 2, 2016
sbrannen added a commit to sbrannen/junit5 that referenced this issue May 2, 2016
This commit separates the execution of extensions and user code with
regard to test lifecycle callbacks.

Issue: junit-team#232
@sbrannen
Copy link
Member

sbrannen commented May 2, 2016

The work in progress can be viewed here: https://github.com/sbrannen/junit5/commits/issue232-simplified-extension-model

And an official PR is forthcoming.

sbrannen added a commit to sbrannen/junit5 that referenced this issue May 2, 2016
This commit avoids unnecessary streaming and synthesizing of extensions
as lambda expressions for @BeforeAll and @afterall methods. Instead,
@BeforeAll and @afterall methods are now invoked directly using
standard for-loops.

Issue: junit-team#232
sbrannen added a commit to sbrannen/junit5 that referenced this issue May 2, 2016
With this commit @beforeeach and @AfterEach methods are looked up and
validated eagerly during the discovery phase instead of late in the game
during the execution phase.

This commit also extracts a new LifecycleMethodUtils class from the
ClassTestDescriptor.

Issue: junit-team#232
@sbrannen
Copy link
Member

sbrannen commented May 3, 2016

See PR #237

@sbrannen
Copy link
Member

sbrannen commented May 6, 2016

Merged into master in 434a360.

@sbrannen sbrannen closed this as completed May 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants