Update the references in contributor testing documentation to refer to pytest instead of unittest.

The testing documentation page currently shows examples of using the unittest framework to create and write tests. However,  Freeseer is moving towards pytest for unit testing. Therefore, the documentation page should be updated to refer to pytest instead of unittest. For example, python examples that show how to extend the existing test set with the unittest module should be updated to reflect the pytest module.

related #420 
related #484 
fix #566 
I mean this, http://pytest.org/latest/goodpractises.html#conventions-for-python-test-discovery but I guess that is not clear. Should I just add a link to this conventions page?
e.g.
``pytest`` uses `conventional <http://pytest.org/latest/goodpractises.html#conventions-for-python-test-discovery>`_ unit test discovery methods to find ``unittest.TestCase`` and ``pytest`` test modules.