Juju’s unit tests are primarily written with the
gocheck library in mind. A recent pull request from @rogpeppe raised the possibility of using
quickcheck within Juju code. That PR has been approved by @cmars, but I would like to pause and gain consensus before we take the decision to incorporate it into Juju code.
@manadart has added some detailed thinking into our unit test setup recently:
quickcheck, Rog has written a good overview of
quickcheck. It feels like step forward technically—love the idea of better pretty printing especially—but I’m still wary that another partially-implemented improvement will lead to greater fragmentation in the code base.