speccer 0.7.5

Basic Specification Syntax

A module specification could look something like this:

myclass.spec: (tests myclass.py)

set up
    c = myclass.MyClass()

adds two and two
    c.add(2,2) == 4

adds negatives
    c.add(10, -10) == 0

fails adding int and string
    c.add(10, 'foo') raises TypeError

It looks pretty much like any other test you may have seen before. The syntax may be a bit lighter, though. As a test author you can focus on the essential while writing the assertions. In addition it’s a bit nicer to read this way.

Note that it’s possible to mix regular Python code within the tests. This might not work in all cases, though, and should be reported.

“set up” is a predefined test method that is run before each specification. This way you can set up some objects that are available for each test.

Each specification contains a name and some actual code asserting something. I have listed available assertions below:

• ==, is equal

• !=, is not equal

• ~=, is almost equal

• !~=, is not almost equal

• >, bigger than

• >=, bigger than or equal

• <, smaller than

• <=, smaller than or equal

• x < y < z, multiple inequalities (mix with equality as you want)

These assertions map directly to ones available in Python’s unittest module. If some of those seem weird to you, see http://docs.python.org/library/unittest.html .

Changelog

• 0.7.5 - Made it possible to define functions between test definitions and made the runner more robust altogether. Now it’s possible to separate tests to another directory. In addition it’s possible to run tests simply by passing this directory to the runner (ie. run_specs tests).

License

Speccer is available under MIT license. See LICENSE for more details.