@@ -25,7 +25,7 @@ We write tests using `unittest` python official module. The tests are separated
...
@@ -25,7 +25,7 @@ We write tests using `unittest` python official module. The tests are separated
- The `unit` module : The tests contained here are unit tests. They use massively mocking and magic mocking of objects. This is where we test mainly the `core` classes and methods.
- The `unit` module : The tests contained here are unit tests. They use massively mocking and magic mocking of objects. This is where we test mainly the `core` classes and methods.
- The `functional` module : The tests contained here are functional tests. They do not use mocking and magic mocking of objects. Instead, they mock ucoin nodes using the server mock in `sakia.tests.mocks.server.py`. In the module `tests.mocks.bma` you can find many already existing mocks of nodes to tests some specific community situations.
- The `functional` module : The tests contained here are functional tests. They do not use mocking and magic mocking of objects. Instead, they mock ucoin nodes using the server mock in `sakia.tests.mocks.server.py`. In the module `tests.mocks.bma` you can find many already existing mocks of nodes to tests some specific community situations.
If you test needs an asynchronous loop, you need your class to inherit `unittest.TestCase`**and**`QuamashTest`. Just add the following calls to your `setUp` and `tearDown` methods :
If your test needs an asynchronous loop, you need your class to inherit `unittest.TestCase`**and**`QuamashTest`. Just add the following calls to your `setUp` and `tearDown` methods :