spec
spec copied to clipboard
Specification-style nosetests output for Python
Right now, the old Spec plugin's behavior of turning `CamelCaseNames` into `Camel case names` is still in effect. I don't really like this, but recognize it can be useful in...
It's not a big deal, since I can output coverage report manually afterwards, but it would be nice to make 2 plugins behave well together.
E.g.: ``` python class Outer(Spec): def setup(self): print "foo" def a_test(self): assert True class inner: def another_test(self): assert True ``` Running this file will see `setup()` run 2x during execution...
The multiprocess plugin mentions that it might not play nice with other plugins... ``` ====================================================================== ERROR: Failure: AttributeError ('SpecPlugin' object has no attribute 'stream') ---------------------------------------------------------------------- Traceback (most recent call last):...
Am looking into #28 but struggling to get the test suite to pass as a first step. It would be useful if some basic contributing instructions were added to the...
I would find it useful if the spec output included the module docstring as well. This would let me set some context for the following TestCases. ### Example For example,...