Requirement tracing automation

[GabyUnalaq]

Description

After a developer implements a feature and requirements for it or links existing ones, they need to check that the changes are ok from the requirement tracing point of view. This is not intuitive and in the current state, it's hard to check manually. Also, this cannot be automated, for a github action that runs on pull requests and so on.

Goals

There exists a method that checks and prints on the console whether there are new errors in the requirements tracing report than before.

One suggestion would be to have a configuration file inside the project that contains the current number of errors of the tracing, and the method compares to that.

Also, using this, we could have it also automated: if the number is not equal, something is wrong and the developer either introduced problems in the requirements or solved them and must lower the count from the config.

Concept

To be done.

Final result

Summary

To be filled when the final solution is sketched.

Tasks

• Think of a concept
• Implement and check the solution
• Add it as a github action