Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Midje provides a migration path from clojure.test to a more flexible, readable, abstract, and gracious style of testing

Fetching latest commit…

Octocat-spinner-32-eaf2f5

Cannot retrieve the latest commit at this time

Octocat-spinner-32 bin
Octocat-spinner-32 downloads
Octocat-spinner-32 emacs
Octocat-spinner-32 examples
Octocat-spinner-32 src
Octocat-spinner-32 test
Octocat-spinner-32 videos
Octocat-spinner-32 .gitignore
Octocat-spinner-32 CONTRIBUTORS.md
Octocat-spinner-32 HISTORY.md
Octocat-spinner-32 LICENSE
Octocat-spinner-32 NOTES
Octocat-spinner-32 README.md
Octocat-spinner-32 Rakefile
Octocat-spinner-32 project.clj
README.md

About Midje

Midje is a test framework for Clojure that emphasizes mocking and ease of use. It supports three levels of syntactic sugar:

  • Unprocessed None at all. You work with maps. For the person who hates my style of sugaring and wants to write her own.

  • Semi-sweet Here's a simple Midje test:

     (expect (numerical-reverser 103) => 301)
    

    I use the arrows because I think of tests as examples. When people show snippets of code as examples, they often use an arrow to separate what you type from what you should expect to see. The Midje line above says "After numerical-reverser is given 103, the test should see it return 301."

    In that form, Midje does the same thing as clojure.test. (Indeed, it uses clojure.test's reporting mechanism.) If, however, you want numerical-reverser to use a function that hasn't been coded yet, you can fake out that function like this:

    (expect (numerical-reverser 103) => 301
       (fake (string-reverser "103") => "301"))
    

    In the second line, the arrow signifies that when string-reverser is given "103", we know its caller will get back "301"

    The semi-sweet style does nothing more than add the expect and fake macros, which are ways of generating the maps the unprocessed style expects while themselves not being too hard to generate from more ambitious macros.

  • Sweet The style I like to use. A "little language" for top-down test-driven development, which repaints Freeman and Pryce's Growing Object-Oriented Software, Guided by Tests to the functional landscape. There, I like to think of TDD as building a web of interrelated facts. For example, here's a fact about numerical-reverser:

       (fact 
          (numerical-reverser 103) => 301)
    

    But that fact is only true for this implementation provided something else is true for string-reverser:

      (fact
        (numerical-reverser 103) => 301
        (provided 
          (string-reverser "103") => "301"))
    

For the impatient

You can easily see Midje in action and fiddle with some tests. You don't even need Clojure installed. Here's how:

  • Click here.
  • In a shell, go to the directory your browser unpacked the example into. It should be named examples.
  • For a sweet example, go to examples/sweet-examples/basic/. For a semi-sweet example, go to examples/semi-sweet-examples.
  • Type "./run". (Windows users, see README.html)
  • To change the tests, edit test/*/core_test.clj.

You can download everything to get more examples.

Documentation

  • This heavily annotated example of the sweet style is the place to look.

  • Another example contains complete descriptions of the semi-sweet style.

  • In the unprocessed style, both calls with their expected results and expectations for calls of faked functions are defined by maps. You can find the format by looking at the definitions of fake and call-being-tested in midje/semi_sweet.clj. The function that does the actual work is expect*. Its first argument is the map in the call-being-tested format, followed by zero or more maps in the fake format.

Community

The mailing list

The wiki is growing documentation about such things as Emacs support and details of use.

Something went wrong with that request. Please try again.