Ufotest

------------------

Added

- unittests in "tests/test_build.py", which are concerned with testing the build process.
- unittests in "tests/test_config.py", which are concerned with testing the functionality exposed by the config module
- Added "FigureTestResult" which allows to add a matplotlib figure directly as the result of a test.
- Added camera test "RepeatedResetTest"
- Added camera test "RepeatedFrameTest"
- Added camera test "CalculatePairNoiseTest"
- Added camera test "RepeatedCalculatePairNoiseTest"

Changes

- The "serve" command now has the option "host" which enables the specification of a different host IP address to bind
the web server to.
- The joining of paths is now integrated into the "get_path" function within the config module.
- The "flash" command now provides more output and the command produces an accurate return code in the case of an error
- Renamed the main method of the BuildRunner from "build" to "run". Added the option to skip the clone and flash steps
(for testing purposes). Furhtermore the method does not return a build report anymore, it has to be seperately
constructed.
- Deprecated "execute_script" with new version "run_script"
- The "test" command now has better console output and actually returns a meaningful error code
- The "init" command now has a flag "update" which only replaced the static assets and leaves the rest of the
installation intact.

Fixes

- Fixed the ufotest unittests to work with the new system of using the TestContext to construct the TestRunner
- Now only importing matplotlib exactly before the frame is actually to be displayed, because previously the "frame"
command would break in a headless SSH session, even if the frame was not even intended to be displayed...
- The "ci build" command now actually uses the test suite which is passed as the argument. Previously it would always
use the default option defined within the config file.
- Attempting to release the build lock when it is not locked not raises the appropriate exception.
- Attempting to construct a test report from a test context without an actual test run being executed before now raises
the appropriate exceptions
- The build lock is now uses the correct folder which can be changed at runtime.
- The build process now properly fails when the flash command fails.
- BuildWorker process now does not crash when a KeyboardInterrupt is received.
- BuildWorker process does not crash when the build process fails and also not when the email sending fails.
- If test suite is currently processing, one cannot access the test archive list in the web interface
presumably because the test folder already exists but no reports have been saved to it. The best course for
fixing this would be to prevent a crash for an empty test folder alltogether.
- Build and test reports are now properly sorted by start date within the web interface
- FIXED: The test are not executed in the order in which they are specified in the config file
- FIXED: Not necessarily a bug with this code but with the way the camera works: I feel like there is a problem with how the
decoding of the images works. I feel like all the images accumulate within the internal buffer of the camera and they
are ALL being read out with each call to ipedecode?

------------------

Fixes

- Now actually using the config.static in the jinja templates, which enables the assets to be loaded correctly.

------------------

Changes

- The flask server now binds to "0.0.0.0" which is required to access it from an outside scope
- TODO: Add an option to the "serve" command so that this can be overwritten

Additions

- An API route for gitlab push webhooks
- An adapter class to format the data from the gitlab webhook correctly

------------------

Changes

- Changed the date format in the HISTORY.rst file
- Changed the default port from 2424 to 8030

------------------

Additions

- Created a new system for handling the builds. previously any build which was triggered while another one was still
running would be rejected. Now there is a build Queue. When a build is triggered, it is added to this queue, which
is essentially just a json file with a list. Then there is a separate process started by the "serve" command which
only checks this queue and executes the build requests saved within.

Changes

- Fixed: The stylesheet for the build report html template was not linked to correctly.
- Fixed: There was an issue where the program would crash if two build would be triggered at the same hour and minute
of the day since they would attempt to create folders with the same name. Added the build commit and the second of
to the folder name format to fix.
- Fixed the bug that a build would not save the test reports properly.
- Fixed the build report url within the report email.

Documentation

- Updated the section about continuous integration.

-------------------

Additions

- Added a test result class which allows to add images as a result.
- Added a test result class which allows to add dicts as a result.
- Test case which simply requests a frame from the camera and adds the image to the test report.
- Test case which requests frame and calculates simple statistics for it.

Changes

- Reworked the "mock" test case to now return a combined test result of one test result object for each available
test result class. The mock test case thus became a way of testing test results classes.
- Fixed an error with including the static css files within the HTML templates of the CI server.
- Fixed the combined test result not having an html conversion.
- Changed the "serve" command: Now it has not arguments anymore. Both the hostname and the port now have to be defined
in the config file. I realized that the html files for the reports are being created in separate instances of the
application, which are not the running server and thus do not know the hostname or the port. This has lead to
errors in the creation of the absolute url links within the html templates.

Documentation

- Changed the documentation for the "serve" command again