Support for writing tests, particularly in a Zope3/ZTK environment, using zope.testing (nose2 may also work, but is not recommended).
Complete documentation is hosted at https://ntitesting.readthedocs.io/
nti.testing can be installed using pip, either from the git repository or from PyPI:
pip install nti.testing
Matchers can be imported from the
is_false check the
bool value of a supplied
object (we're using literals for explanation purposes, but it
obviously makes more sense, and reads better, when the matched object
is a variable, often of a more complex type):
>>> from hamcrest import assert_that, is_ >>> from nti.testing.matchers import is_true, is_false >>> assert_that("Hi", is_true()) >>> assert_that(0, is_false())
Next we come to matchers that support basic use of
We can check that an object provides an interface and that a factory implements it:
>>> from zope.interface import Interface, Attribute, implementer >>> class IThing1(Interface): ... pass >>> class IThing2(Interface): ... pass >>> class IThings(IThing1, IThing2): ... got_that_thing_i_sent_you = Attribute("Did you get that thing?") >>> @implementer(IThings) ... class Thing(object): ... pass >>> from nti.testing.matchers import provides, implements >>> assert_that(Thing(), provides(IThings)) >>> assert_that(Thing, implements(IThings))
The attentive reader will have noticed that
IThings defines an
attribute that our implementation doesn't actually provide. This is
where the next stricter check comes in.
the interface machinery to determine that all attributes and methods
specified by the interface are present as described:
>>> from nti.testing.matchers import verifiably_provides >>> assert_that(Thing(), verifiably_provides(IThing2, IThing1)) >>> assert_that(Thing(), verifiably_provides(IThings)) Traceback (most recent call last): ... AssertionError:... Expected: object verifiably providing IThings but: <class 'Thing'> failed to provide attribute "got_that_thing_i_sent_you" from IThings <BLANKLINE>
zope.interface can only check whether or not an attribute or
method is present. To place (arbitrary) tighter constraints on the
values of the attributes, we can step up to
zope.schema and the
>>> from zope.schema import Bool >>> class IBoolThings(IThing1, IThing2): ... got_that_thing_i_sent_you = Bool() >>> @implementer(IBoolThings) ... class BoolThing(object): ... pass
validly_provides is a superset of
>>> from nti.testing.matchers import validly_provides >>> assert_that(BoolThing(), validly_provides(IThing1, IThing2)) >>> assert_that(BoolThing(), validly_provides(IBoolThings)) Traceback (most recent call last): ... AssertionError:... Expected: (object verifiably providing IBoolThings and object validly providing <InterfaceClass ....IBoolThings>) but: object verifiably providing IBoolThings <class 'BoolThing'> failed to provide attribute "got_that_thing_i_sent_you" from IBoolThings <BLANKLINE>
For finer grained control, we can compare data against schema fields:
>>> from nti.testing.matchers import validated_by, not_validated_by >>> field = IBoolThings.get('got_that_thing_i_sent_you') >>> assert_that(True, is_(validated_by(field))) >>> assert_that(None, is_(not_validated_by(field)))
aq_inContextOf matcher uses the concepts from Acquisition to
check parent/child relationships:
>>> from nti.testing.matchers import aq_inContextOf >>> class Parent(object): ... pass >>> class Child(object): ... __parent__ = None >>> parent = Parent() >>> child = Child() >>> child.__parent__ = parent >>> assert_that(child, aq_inContextOf(parent))
Support for test fixtures can be found in
base package includes fully-fleshed
out base classes for direct use, while the
layers package includes
mixins that can be used to construct your own test layers.
base package makes a distinction between "normal" and "shared"
fixtures. Normal fixtures are those that are used for a single test
case. They are established via
setUp and torn down via
In contrast, shared fixtures are expected to endure for the duration
of all the tests in the class or all the tests in the layer. These are
best used when the fixture is expensive to create. Anything that
base.AbstractSharedTestBase creates a shared fixture.
Through the magic of metaclasses, such a subclass can also be assigned
layer property of another class to be used as a test layer
that can be shared across more than one class.
The most important bases are
base.SharedConfiguringTestBase. These are both fixtures for
configuring ZCML, either from existing packages or complete file
paths. To use these, subclass them and define class attributes
set_up_packages and (if necessary)
>>> from nti.testing.base import ConfiguringTestBase >>> import zope.security >>> class MyConfiguringTest(ConfiguringTestBase): ... set_up_packages = ( ... 'zope.component', # the default configuration by name ... # a named file in a named package ... ('ftesting.zcml', 'zope.traversing.tests'), ... # an imported module ... zope.security, ... # Our own package; in a test, this will mean the parent ... # package ... ".")
We would then proceed to write our test methods. The packages that we
specified will be set up and torn down around every test method. In
zope.testing cleanup functions will also run around
every test method.
Having a clock that's guaranteed to move in a positive increasing way
in every call to
time.time is useful.
provides a decorator to accomplish this that ensures values always are
at least the current time and always are increasing. (It is not thread
safe.) It can be applied to functions or methods, and optionally takes
>>> from nti.testing.time import time_monotonically_increases >>> from nti.testing.time import reset_monotonic_time >>> @time_monotonically_increases(0.1) # increment by 0.1 ... def test(): ... import time ... t1 = time.time() ... t2 = time.time() ... assert t2 == t1 + 0.1, (t2, t1) >>> test()