mirror of
https://github.com/google/nomulus.git
synced 2025-05-30 01:10:14 +02:00
bbacdb9704
* Start using JUnit 5 This converts a single test class over to JUnit 5 (YamlUtilsTest). The main differences you'll notice are that @RunWith isn't needed anymore, test classes and test methods can now be package-private, and the @Test annotation comes from the org.junit.jupiter.api package instead of org.junit. There's a lot more differences between 4 and 5 than this that we'll need to keep in mind when converting more test classes; for some more details, see: https://www.baeldung.com/junit-5-migration In order to allow JUnit 4 and 5 test classes to coexist, I've had to add two new dependencies, org.junit.jupiter:junit-jupiter-engine and org.junit.vintage:junit-vintage-engine, which exist in addition to junit:junit for now. Eventually, once we've completed migrating over all JUnit 4 test classes, then we can remove junit and junit-vintage-engine and just be left with junit-jupiter-engine. * Delete no longer needed lockfiles * Merge branch 'master' into first-junit5 |
||
|---|---|---|
| .. | ||
| annotationProcessor.lockfile | ||
| apt.lockfile | ||
| archives.lockfile | ||
| buildscript-classpath.lockfile | ||
| checkstyle.lockfile | ||
| compile.lockfile | ||
| compileClasspath.lockfile | ||
| compileOnly.lockfile | ||
| default.lockfile | ||
| deploy_jar.lockfile | ||
| errorprone.lockfile | ||
| errorproneJavac.lockfile | ||
| jacocoAgent.lockfile | ||
| jacocoAnt.lockfile | ||
| runtime.lockfile | ||
| runtimeClasspath.lockfile | ||
| testAnnotationProcessor.lockfile | ||
| testApt.lockfile | ||
| testCompile.lockfile | ||
| testCompileClasspath.lockfile | ||
| testCompileOnly.lockfile | ||
| testRuntime.lockfile | ||
| testRuntimeClasspath.lockfile | ||