You will want to write your tests for each module in
Testing functionality that is useful for multiple tests can be found in
To actually execute tests, run
Note that this deletes and re-creates the db from scratch each time,
so you may want to pass the
-k option when developing tests as it significantly reduces run-time.
Coverage information is auto-generated at Coveralls This is useful for finding files with insufficient coverage, so you can focus your test writing more accurately.
Looking at pre-existing tests can give you a good idea how to structure your tests.
IonTestCase class is a wrapper around the standard Django test class.
It handles some ion-specific logic, such as mocking out ldap queries.
Here is an bare-bones example of the basic layout for a test:
from ...test.ion_test import IonTestCase class ModuleTest(IonTestCase): def test_module_function(self): # Put your tests here self.assertEqual(1, 1)