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

Migrate tests to JUnit 5.4.0 #2493

Merged
merged 4 commits into from
Mar 3, 2019
Merged

Migrate tests to JUnit 5.4.0 #2493

merged 4 commits into from
Mar 3, 2019

Conversation

arteam
Copy link
Member

@arteam arteam commented Sep 15, 2018

JUnit5 has been slowly getting among the community over the past years and it looks like stable enough for us to migrate.

@arteam arteam force-pushed the junit5-migration branch 5 times, most recently from b9b334b to 2540701 Compare September 15, 2018 22:16
@arteam arteam added this to the 2.0.0 milestone Sep 15, 2018
@arteam arteam force-pushed the junit5-migration branch 2 times, most recently from 42f451b to 674cf72 Compare September 23, 2018 19:57
@Tibor17
Copy link

Tibor17 commented Nov 4, 2018

You should use higher version maven-surefire-plugin:2.22.1 because this is able to work with any JUnit5 version. The JUnit5 provider should not be used. It's enough to use the JUnit5 engine in POM dependencies.

@joschi joschi changed the title WIP: Migrate tests to JUnit5 Migrate tests to JUnit 5.4.0 Feb 24, 2019
@joschi joschi self-assigned this Feb 24, 2019
@joschi joschi added the feature label Feb 24, 2019
@joschi joschi force-pushed the junit5-migration branch 2 times, most recently from 6309610 to f5a675c Compare February 24, 2019 21:20
@jplock
Copy link
Member

jplock commented Mar 1, 2019

Is there a way to re-run the tests on Appveyor?

@joschi joschi force-pushed the junit5-migration branch 6 times, most recently from 6d8177a to ddd435e Compare March 2, 2019 17:27
* CustomRequestLogPatternIntegrationTest
* RequestLogPatternIntegrationTest

Example exception (shortened):

ERROR [2019-03-02 10:38:12,736] org.junit.jupiter.engine.execution.JupiterEngineExecutionContext: Caught exception while closing extension context: org.junit.jupiter.engine.descriptor.MethodExtensionContext@72bca894
java.io.IOException: Failed to delete temp directory C:\Users\appveyor\AppData\Local\Temp\1\junit6846106039914940147. The following paths could not be deleted (see suppressed exceptions for details): , example-new-app-not-additive.log, example-new-app.log, example.log
at org.junit.jupiter.engine.extension.TempDirectory$CloseablePath.createIOExceptionWithAttachedFailures(TempDirectory.java:206)
at org.junit.jupiter.engine.extension.TempDirectory$CloseablePath.close(TempDirectory.java:167)
Suppressed: java.nio.file.DirectoryNotEmptyException: C:\Users\appveyor\AppData\Local\Temp\1\junit6846106039914940147
	at org.junit.jupiter.engine.extension.TempDirectory$CloseablePath$1.deleteAndContinue(TempDirectory.java:187)
	at org.junit.jupiter.engine.extension.TempDirectory$CloseablePath$1.postVisitDirectory(TempDirectory.java:182)
	at org.junit.jupiter.engine.extension.TempDirectory$CloseablePath$1.postVisitDirectory(TempDirectory.java:173)
	at org.junit.jupiter.engine.extension.TempDirectory$CloseablePath.deleteAllFilesAndDirectories(TempDirectory.java:173)
	at org.junit.jupiter.engine.extension.TempDirectory$CloseablePath.close(TempDirectory.java:165)
	... 44 common frames omitted
Suppressed: java.nio.file.FileSystemException: C:\Users\appveyor\AppData\Local\Temp\1\junit6846106039914940147\example.log: The process cannot access the file because it is being used by another process.
@joschi joschi merged commit 89712d2 into master Mar 3, 2019
@joschi joschi deleted the junit5-migration branch March 3, 2019 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants