A collection of test helpers, additional assertions, and the like.
This package collects various helpers for writing tests.
An assertion which is very helpful when using Testbrowser with unittest.TestCase (instead of doctests).
class MyTest(unittest.TestCase, gocept.testing.assertion.Ellipsis): # [...] self.assertEllipsis('...bar...', 'foo bar qux') # -> nothing happens self.assertEllipsis('foo', 'bar') # -> AssertionError: Differences (ndiff with -expected +actual): - foo + bar self.assertNotEllipsis('foo', 'foo') # -> AssertionError: "Value unexpectedly matches expression 'foo'."
To use, inherit from gocept.testing.assertion.Ellipsis in addition to unittest.TestCase.
class MyTest(unittest.TestCase, gocept.testing.assertion.String): def test_something(self): self.assertStartsWith('foo', 'foobar') # --> pass self.assertEndsWith('bar', 'foobar') # --> pass self.assertStartsWith('qux', 'foobar') # --> fail self.assertEndsWith('qux', 'foobar') # --> fail
The opposite of assertRaises(), this is an assertion that makes some tests more readable. As assertRaises(), it can be used as as context manager, too:
class MyTest(unittest.TestCase, gocept.testing.assertion.Exceptions): # [...] self.assertNothingRaised(do_something, 1, 2, 3) with self.assertNothingRaised(): do_something(1, 2, 3)
class MyTest(unittest.TestCase): def setUp(self): self.patches = gocept.testing.mock.Patches() def tearDown(self): self.patches.reset() def test_something(self): compile = self.patches.add('re.compile')
It offers three methods:
Note that gocept.testing does not declare a dependency on mock to be as lightweight as possible, so clients need to do that themselves.
If you want to save typing, you can mix gocept.testing.mock.PatchHelper into your TestCase, it defines a setUp method that instatiates Patches and a tearDown that calls reset() on it.
This is syntactic sugar around mock.assert_called_with, so you can write:
class MyTest(unittest.TestCase, gocept.testing.mock.Assertions): def test_something(self): dummy = mock.Mock() dummy(True) self.assertCalledWith(dummy, True)
gocept.testing.mock.Property is syntactic sugar directly lifted from the mock documentation that allows you to patch properties like this:
class Dummy(object): @property def foo(self): return False with mock.patch('Dummy.foo', gocept.testing.mock.Property()) as foo: foo.return_value = 'something else'
This has nothing to do with mocks, it’s a convenience helper for setting and automatically resetting attributes of objects:
class MyTest(unittest.TestCase): def setUp(self): self.patches = gocept.testing.patch.Patches() self.subject = MyClass() def tearDown(self): self.patches.reset() def test_something(self): self.assertEqual('one', self.subject.foo) self.patches.set(self.subject, 'foo', 'two') self.assertEqual('two', self.subject.foo)
This allows to call a method and reset it later on automatically. At the moment, only methods that take a single parameter are supported, by passing in both the old value (to which it should be reset) and the new value:
class MyTest(unittest.TestCase): def setUp(self): self.patches = gocept.testing.patch.Patches() def tearDown(self): self.patches.reset() def test_something(self): self.patches.call( zope.component.hooks, 'setSite', zope.component.hooks.getSite(), new_site)
gocept.testing.patch.Dict is a context manager allowing to change values in a dict. It restores the original dict at exit. E. g. it can be used to temporarily change values in os.environ:
>>> with gocept.testing.patch.Dict(os.environ, foo='bar', qwe='asdf'): print os.environ.get('foo') bar >>> print os.environ.get('foo') None
gocept.testing.fixture.TempDir encapsulates the common pattern to create a temporary directory and delete it after the test has run. The name of the directory is avaliable as self.tmpdir. Note that since unittest.TestCase does not call super, you need to mix in TempDir first:
class MyTest(gocept.testing.fixture.TempDir, unittest.TestCase): def test_something(self): self.assertTrue(os.path.isdir(self.tmpdir))
gocept.testing.mtime.Newer checks that generated files are at least as new as their source counterparts (similar like make works):
class MyTest(gocept.testing.mtime.Newer, unittest.TestCase): source_ext = '.js' target_ext = '.min.js' message = 'run jsmin to correct this' def test_minified_js_files_are_younger_than_non_minified_ones(self): self.check_files(pkg_resources.resource_filename( 'my.package', 'resources/js'))
The mercurial repository of the source code as well as the issue tracker are available at <https://bitbucket.org/gocept/gocept.testing>.
- Make assertNotEllipsis() compatible with py.test.
- Declare Python 3.3 support.
- Remove retry decorator, it is rather useless since it does not take setUp/tearDown into account.
- Add retry decorator that runs flaky tests several times and only fails when they fail each time.
- Use py.test instead of zope.testrunner for this package’s own tests.
- Python 3 compatibility.
- Depend on setuptools rather than distribute now that the projects have merged.
- Use current buildout and recipes for development.
- Fix Python-2.6 compatibility of our own test suite.
- Introduce PatchHelper.
- Add newer mtime check.
- .patch.Dict did not restore the keys if an exception occured while the with call.
- Fixed documentation and faulty 1.5 release.
- Add .patch.Dict, a dict patching context manager.
- Add TempDir fixture.
- Add assertStartsWith, assertEndsWith.
- Allow assertEllipsis to work with mixed unicode/bytes argument (assuming the bytes are UTF-8, as they are with zope.testbrowser).
- Display original traceback in assertNothingRaised.
- Add patch helper for attributes and simple callables.
- Make Python-3 compatible (at least syntactically).
- Add Patches context for mock (upstream implementation pending, see <http://code.google.com/p/mock/issues/detail?id=30>)
- Add assertCalledWith.
- Add mock.Property.
- Add assertNothingRaised.
- first release: assertEllipsis