google-nomulus/common
Ben McIlwain 3139a2ffee Start using JUnit 5 (#488)
* 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
2020-02-19 18:29:59 -05:00
..
gradle/dependency-locks Start using JUnit 5 (#488) 2020-02-19 18:29:59 -05:00
src Upgradle JUnit to 4.13 (#442) 2020-01-14 10:54:09 -05:00
build.gradle Start using JUnit 5 (#488) 2020-02-19 18:29:59 -05:00
README.md Break circular dependency between core and util (#379) 2019-11-21 15:36:55 -05:00

Summary

This project holds some of the general-purpose utility classes that do not rely on the registry domain model.

This is an intermediate step in untangling the circular dependencies between :core and :util subprojects.