Specter
Specter copied to clipboard
jmvrbanac
Specter is a Python BDD testing library which takes inspiration from RSpec and Jasmine
The `@metadata` allows the user to specify a list of tests to include based on their tag. It would be handy to also be able to do the opposite. Essentially,...
If the Incomplete decorator is at the end of the execution chain ```python @incomplete @metadata(category='positive') def can_retrieve(self): pass ``` It results in output like: ``` --snip-- ∟ DECORATOR ONCALL --snip--...
Python Version: 3.4.5 Specter Version: 0.5.1 This seems to occur whenever an expectation is in a method that doesn't belong to the Spec. This following output doesn't really make sense,...
This doesn't happen for all nested functions; however, it does in this specific case: Example: ``` def my_test(self): something = [] def faux_info(x): something.append(x) logger = stub(info=faux_info) logger.info('my thing') expect(something[0]).to.equal('something')...
I'm wondering if this issue is due to an issue with Pynsive's module loading process as this resembles the issue that I fixed in Pynsive to support coverage in Python...
Output from a test run: ``` ✘ app._router.find('/v1/something')[0] not to be None app._router.find('/v1/something')[0]: None Expected: None ``` This should say "Expected not to be:" to match the negative conditional.
I'm guessing this has something to do with the face that SystemExit doesn't inherit from Exception. This needs to get fixed.
If the spec folder isn't a real python package, it generates a rather generic import error. This issue was discovered by @AMeng in issue #54. While we discovered that he...
Currently, Specter doesn't capture the output for code that occurs during a test. It would be nice to have the option to suppress it. This is was it currently looks...