This is the second part of a series that explores clojure.spec, property-based testing, and how those tools can be used to test Datomic. Check out part 1 for an introduction to clojure.spec and property-based testing. All of the code from this post is in the example repo
As we discussed in the first post, property-based testing works well for pure functions but that excludes a good chunk of code we would like to thoroughly test such as code that makes updates to a database. I also hinted that Datomic is uniquely suited to be tested by property-based tests.
Continue reading “Property-Based Testing with Clojure and Datomic – Part 2”
This is the first part of a multi-part series that explores clojure.spec, property-based testing, and how those tools can be used to test Datomic. This post serves mainly as an introduction to property-based testing and clojure.spec. Check out part 2 for the introduction of Datomic property-based testing.
Clojure.spec was recently released and the Clojure community is diving into it to see how specs can improve their programs. One of the more interesting design decisions made for clojure.spec is the connection between specs and property-based testing via another Clojure contrib library:
Continue reading “Property-Based Testing with Clojure and Datomic – Part 1”
Abstract: Keeping a test suite separate from the application itself has several benefits, including adopting a user’s perspective, (potentially) identical tests for development or production, load testing, and flexibility to totally rewrite the app.
Continue reading “The benefits of writing a separate test suite for your app”