Generic golden testing library with support for MUnit and Weaver.
ℹ️ The name "dorado" is the Spanish for "golden".
The main idea behind golden tests is to make it as explicitly as possible when we are breaking the JSON protocol, either by changing or deleting a field, or by adding new event or removing an existing one.
Ideally, we would achieve this goal by keeping it simple and have meaningful diffs when submitting a PR that breaks the protocol one way or another.
Find out the latest version above in the Maven badge as well under releases.
For munit:
libraryDependencies += "dev.profunktor" %% "dorado-munit-core" % Version
libraryDependencies += "dev.profunktor" %% "dorado-munit-circe" % VersionFor weaver:
libraryDependencies += "dev.profunktor" %% "dorado-weaver-core" % Version
libraryDependencies += "dev.profunktor" %% "dorado-weaver-circe" % VersionThis is the most minimal library that supports golden testing. As such, it expects a few things from the user.
Let's say we have the following ADT, namely Event, as demonstrated under modules/examples.
@newtype case class EventId(value: UUID)
@newtype case class Timestamp(value: Instant)
sealed trait Event
object Event {
final case class One(id: EventId, foo: String, createdAt: Timestamp) extends Event
final case class Two(id: EventId, bar: Int, createdAt: Timestamp) extends Event
implicit val jsonEncoder: Encoder[Event] = deriveEncoder
implicit val jsonDecoder: Decoder[Event] = deriveDecoder
}In this case, we use Circe's semi-automatic derivation for our JSON instances.
So, to add the first tests, we need to create json files for each event's format, under the test/resources/ folder. We can create sub-directories to organize things a little better. For example, we would create an event folder and the files One.json and Two.json within it.
.
├── resources
│ └── event
│ ├── One.json
│ └── Two.json
In our example, we can generate the JSON from a simple example, or even from Scalacheck's generators, if we want to. That's up to the user. In this case, we have created the following content for such JSON files.
This is One.json.
{
"One" : {
"id" : "a1651f08-72f2-4264-85be-6ee6b1b77e6c",
"foo" : "test1",
"createdAt" : "2020-10-25T09:27:26.270734Z"
}
}And this is Two.json.
{"Two":{"id" :"a1651f08-72f2-4264-85be-6ee6b1b77e6c","bar":123,"createdAt":"2020-10-25T09:27:26.270734Z"}}Yes! As you can see, the format does not matter, as long as the JSON is valid and can be decoded to our existing datatype.
All we have to do next to create a roundtrip JSON conversion test is the following.
import dorado.munit.circe.CirceDoradoSuite
class EventGoldenSuite extends CirceDoradoSuite[Event]("/event")Or using Weaver:
import dorado.weaver.circe.CirceDoradoSuite
object EventGoldenSuite extends CirceDoradoSuite[Event]("/event")It will read all the JSON files under test/resources/event/, try to parse every one of them with the decoder for Event, and finally compare the decoded values against the original inputs (disregarding formatting) to make valuable tests.
This is the output, in case of success.
sbt:examples> testdev.profunktor.golden.EventGoldenSuite:
+ dev.profunktor.golden.Event roundtrip conversion 0.18s
[info] Passed: Total 1, Failed 0, Errors 0, Passed 1In case of a decoding failure, you might see something like this (not the best error message but that might be improved in future iterations).
sbt:examples> test
dev.profunktor.golden.EventGoldenSuite:
==> X dev.profunktor.golden.EventGoldenSuite.dev.profunktor.golden.Event roundtrip conversion 0.165s munit.FailException: /home/gvolpe/workspace/golden/modules/core/src/main/scala/munit/golden/GoldenSuite.scala:42 Error: Attempt to decode value on failed cursor: DownField(foo),DownField(One). Input: {"One":{"id":"a1651f08-72f2-4264-85be-6ee6b1b77e6c","fo":"test1","createdAt":"2020-10-25T09:27:26.270734Z"}}
41: jsonDecoder(json) match {
42: case Left(e) => fail(e)
43: case Right(e) => assertEquals(jsonEncoder(e), json)In case of non-exhaustive failure check (e.g. missing JSON file for Event.Two), you'll get an error message as the one below.
sbt:examples> test
dev.profunktor.golden.EventGoldenSuite:
==> X dev.profunktor.golden.EventGoldenSuite.dev.profunktor.golden.Event roundtrip conversion 0.196s munit.FailException: /home/gvolpe/workspace/golden/modules/core/src/main/scala/munit/golden/GoldenSuite.scala:73
72: }
73: assert(
74: check.check(checks.toSet),
> Non-exhaustive matching. Processed branches:
- dev.profunktor.golden.Event.One
at munit.FunSuite.assert(FunSuite.scala:11)
at munit.golden.GoldenSuite.$anonfun$new$1(GoldenSuite.scala:73)The CirceDoradoSuite is a convenient modules you can use by adding the corresponding Circe module to your dependencies, though, we could either use MunitDoradoSuite or WeaverDoradoSuite directly.
Dorado abstracts over any JSON library. This is how it is defined:
trait Dorado[A] {
/**
* The JSON decoder function.
*/
def jsonDecoder: String => Either[String, A]
/**
* The JSON encoder function.
*/
def jsonEncoder: A => String
/**
* The path of the directory under the test/resources folder.
*/
def path: String
}Adding new modules for other JSON libraries would be really easy, have a look at dorado-core and their concrete implementations, PRs welcome!
A golden test suite is mainly useful when you have an Algebraic Data Type (ADT) so that's the only thing that this library supports. If you have simple case class, it wouldn't work.
There are a few registered issues with Newtype and Refined. In general, everything works except for a few weird edge cases that I hope can be solved at some point.
AFAIK there's only circe-golden, but please correct me if I'm mistaken by either opening an issue or even better, by creating a PR.
Circe Golden, besides only supporting Circe as the JSON library, it creates a bunch of serialized files with data generated with Scalacheck's generators. These files are then read in subsequent runs of the tests and compared against the newly serialized data, by using the same Scalacheck seed.
The idea is great. However, whenever you make any changes to your model, you need to delete all the generated JSON files so that they are created again with the new version of the protocol. This is far from ideal, since we immediately lose meaningful diffs and it gets harder to keep track of the actual changes in any PR.
Also, at the time of writing (Oct 27th of 2020), Circe Golden only works with sbt - and not with other build tools - due to hard-coded resource paths specifics to sbt.
Conversely, dorado supports any JSON library as well as meaningful diffs when breaking the protocol. It also supports other build tools such as Mill. This is the essence of the project.
Huge thanks to Fabio Labella for the type-level machinery to check for exhaustiveness at runtime.