Report from automated testing this year

For the first time on this team we had our robot code automatically tested using JMockit and azure pipelines to actually run the tests.

Initially getting everyone used to the framework took some time, but after a couple of weeks we had tests for all components of the robot.

We ran into issues when under tight deadlines we found we had no time to complete tests for all the subsystems that we were rushing to complete, especially when each time we added more code we had to modify the tests for unrelated parts of the robot since new mocking would be required.

If we were to continue with automated testing in the future, we would need to improve on a couple of things. The first thing to be improved is the ability to more easily create a method for mocking a certain set of classes for all tests which used things which would change in the future.

The issue documents automated testing with JMockit and Azure Pipelines, but names no files, tests, or entry points. Clarify the desired mocking improvement and its scope before identifying the affected code and defining what completion means.

Written by the indexing model from the issue text.