Unit testing standards and best practices

!!!This is a work in progress!!! This page contains PARPG accepted standards and general guidelines related to unit testing.

Standards

 * Tests for each class should reside in a separate file. File names should be test_.py
 * Test files are stored in /tests directory
 * Test classes should be named Test.py
 * Each test method should have a description comment in the first line of the method. It will be output instead of test method name each time the test is run. This description should be very concise and describe what sort of functionality in which class is tested.
 * Several tests that verify the same kind of functionality and don't require object cleanup between them can be grouped in the same test method (e.g. testCoordinatesManipulation may have several groups of coordinates manipulations and assertions)
 * Initialization common to all test methods of some test class should be moved to setUp method. Common finalization and cleanup should be moved to tearDown. They will run before/after each test method.