Map tests to design input, risk mitigation or user needs

[stefpiatek]

Initial thoughts

A couple of options:

• Require a specific format in docstrtings and run doxygen, doxygen output checks that all tests have been linked to a an issue (using the number of the issue?)
• Have a file within the qw directory which tracks all tests and their linked issues, CI checks if there are any new tests and requires them to be added to the test mapping file

Decision

Settled on having a manual file to track