-
Notifications
You must be signed in to change notification settings - Fork 65
chore: migrate junit3/4 to junit 5 #639
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
base: master
Are you sure you want to change the base?
Conversation
AbstractMojoTestCase based test will be migrate in a seperate PR Signed-off-by: Sandra Parsick <[email protected]>
Signed-off-by: Sandra Parsick <[email protected]>
Signed-off-by: Sandra Parsick <[email protected]>
Signed-off-by: Sandra Parsick <[email protected]>
Signed-off-by: Sandra Parsick <[email protected]>
Signed-off-by: Sandra Parsick <[email protected]>
|
I would like to split such PR - one update in ITs and next with unit tests updates |
|
I will split it tomorrow. |
| @MojoTest | ||
| public class CheckstyleExecutorTest { | ||
| @Inject | ||
| private CheckstyleExecutor executor; | ||
| @Test | ||
| public void testDefaultConfig() throws Exception { | ||
| CheckstyleExecutor executor = (CheckstyleExecutor) lookup(CheckstyleExecutor.class); | ||
| assertNotNull("project null.", executor); | ||
| assertNotNull(executor, "project null."); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like PlexusTest not MojoTest
| // | ||
| // LegacySupport legacySupport = lookup(LegacySupport.class); | ||
| // legacySupport.setSession(newMavenSession(new MavenProjectStub())); | ||
| DefaultRepositorySystemSession repoSession = | ||
| (DefaultRepositorySystemSession) legacySupport.getRepositorySession(); | ||
| repoSession.setLocalRepositoryManager(new SimpleLocalRepositoryManagerFactory() | ||
| .newInstance(repoSession, new LocalRepository(artifactStubFactory.getWorkingDir()))); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Legacy staff is not used by AbstractMavenReport ...
but AbstractMavenReport needs a remote repository to resolve site skin, so it looks like more integration test
There is side effect with such old staff that test is working
I need to discover how to achieve similar effect with new way
also migrates AbstractMojoTestCase to MojoTest.