-
Notifications
You must be signed in to change notification settings - Fork 0
6 DR 20240414
keywords: db, coverage
Storing all tracing related information in a relational database has several benefits. Firstly, the requirement origin must not be updated anymore to store trace data. Secondly, a database allows more complex queries to further analyze the collected data.
Besides creating traces to requirements to connect definition and implementation, Traces in code may set specific logs during testing, to know which requirements are not only implemented, but also tested.
In Rust, procedural macros are used to set traces instead of using [req:<requirement ID>] in comments,
to generate the needed logs with minimal overhead for developers.
Collecting trace data gets more complex than plain regex search,
but using tools like tree-sitter help with trace detection,
because for example commented code will be skipped.
Please create an issue if you found any spelling mistakes.
You may also create an issue if you think the content of this wiki should be improved.
Note: This wiki is managed in its own repository. Any commits made using the edit button will be overwritten.
Note: Issues for the wiki are handled in the mantra repository, but pull requests for the wiki are handled in the mantra-wiki repository.
This wiki is MIT licensed, and works together with mantra.