Connecting Requirements to tests

[i-interprete-on-the-fly]

Hey,
does StrictDoc also aim to enable traceability between the requirements and respective test cases? (and maybe also accommodate for test result display in some format)?

What I currently need would be comprehensive traceability system between Requirements, refined requirements, their source code implementation and also a linkage to test cases.

Edit - To provide more context: I want to introduce this tool for requirements management in the ASPICE relevant projects of my company. I think I could technically represent the test cases as [REQUIREMENT] elements with relations as the tests being the childs of the requirements but I'm not sure if this is the most elegant way and also if you may have another possible solution in mind.

Thank you for this nice tool!

[i-interprete-on-the-fly]

I'll have to adjust my question a bit here. Through taking a closer look at the grammar and the specific relations I saw that I can create [TESTCASE] elements without any hassle and also define a 'verifies' parent relationship between the test case and the requirement. For the part of linking test cases (maybe automatically in the context of CI) I could then use the file location to a test case result summary file with the verdict.
What would be interesting in this scenario is: Have some kind of dynamic field in the test case node which updates according to the linked file content, maybe through so simple condition syntax?

[stanislaw]

I'll have to adjust my question a bit here. Through taking a closer look at the grammar and the specific relations I saw that I can create [TESTCASE] elements without any hassle and also define a 'verifies' parent relationship between the test case and the requirement. For the part of linking test cases (maybe automatically in the context of CI) I could then use the file location to a test case result summary file with the verdict.

Coming back to this one after some time. We have implemented 80%+ of the work needed for the custom grammar elements to be editable in the UI. I say 80%+ because based on the experience the other 20% will be spent on handling the corner cases that were not obvious during the implementation. This means that from now on, the non-requirement nodes should be also editable in the web user interface. We will enable editing of the File links in the UI very soon too.

What would be interesting in this scenario is: Have some kind of dynamic field in the test case node which updates according to the linked file content, maybe through so simple condition syntax?

For this kind of dynamic fields updates, I could think of a command-line interface command or a UI button that scan over all requirements and performs a certain action. Could you give a more concrete example of what you would like see updated: which field should updated with which content?