Documentation: Development environment #442

Author: dennissiemensma

docs/changelog.rst

@@ -17,14 +17,19 @@ Please make sure you have a fresh **database backup** before upgrading! Upgradin
 ----
 
 
-v1.28.0 - 2019-01-03
+v1.28.0 - 2019-01-04
 ^^^^^^^^^^^^^^^^^^^^
 
+.. note::
+
+	This will be the last release for a few months until spring 2019.
+
 **Tickets resolved in this release:**
 
 - [`#571 <https://github.com/dennissiemensma/dsmr-reader/issues/571>`_] Trends klok omdraaien
 - [`#570 <https://github.com/dennissiemensma/dsmr-reader/issues/570>`_] Herinstallatie/verwijdering documenteren
-- [`#442 <https://github.com/dennissiemensma/dsmr-reader/issues/442>`_]  Documentation: Development environment
+- [`#442 <https://github.com/dennissiemensma/dsmr-reader/issues/442>`_] Documentation: Development environment
+- Requirements update
 
 
 ----

docs/development.rst

@@ -118,8 +118,10 @@ The application will be accessible on: ``http://localhost:8000/``.
 Any code changes you make will let the application reload automatically.
 
 
-Tests
------
+Tests and coverage
+------------------
+
+DSMR-reader's test coverage should remain as high as possible. Running tests will also analyze the test coverage in detail. 
 
 The easiest way to run tests is to use the in-memory tests::
 
@@ -136,6 +138,16 @@ To test all database backends, run::
 	source ~/.virtualenvs/dsmrreader/bin/activate
 	./tools/test-all.sh
 
+The test coverage should be visible in the terminal after running tests.
+There are detailed HTML pages available as well, after each test run, in ``coverage_report/html/index.html``. 
+Just open it with your browser to view the test coverage of each file and line.
+
+.. note::
+
+	A side effect of running tests is that it may also regenerate .PO files from the ``docs/`` folder. 
+	If you did not make any changes there, your should just ignore those changed files and revert them.
+	
+
 Translations
 ------------