Add traceability - Githubissues

costateixeira commented 12 months ago

As a test user, I want to document the links between test cases and the requirements, in order to identify which requirements are covered by which cases.

Link can be a number, a string or a URL
This should be a structured information (not narrative) to allow coverage reporting
Should be added to the TDL for being part of the test authoring

costas80 commented 11 months ago

Should be added to the TDL for being part of the test authoring

Indeed, I've added this to our backlog and will update you here when the feature is ready. It will first be available on the nightly build channel, meaning that you will immediately be able to pull the update before waiting for a full release.

costas80 commented 10 months ago

Traceability to specifications from test cases and/or test suites is now supported (available now on the nightly build channel). In the GITB TDL (the XML test description language), a test developer can now specify for both test suites and test cases as part of their metadata element, a new specification element. This includes:

A reference element that identifies the relevant specification section (e.g. a code, chapter number, identifier).
A description element with a brief text description of the relevant specification section.
A link element with a link to the online specification section's documentation.

Each of these elements is optional, meaning that you may specify references as best suits your needs (e.g. only provide a reference code and link). For example, a test case could include the following as a reference to the specification section it covers:

<metadata>
   ...
   <gitb:specification>
      <gitb:reference>EUDI-A1-02</gitb:reference>
      <gitb:description>Security requirements for EUDI wallets.</gitb:description>
      <gitb:link>https://digital-strategy.ec.europa.eu/en/policies/electronic-identification</gitb:link>
   </gitb:specification>
</metadata>

On the UI specification references are presented based on how they are defined (e.g. displaying the reference code as a link or as plain text, followed by the description). This screenshot shows for example specification references for 3 test cases (first one with a reference plus link, second one with reference plus description, third one with link only):

Note that these specification references can be set/edited via test suite upload (reading values from the XML definitions), or also set via the UI:

medigree / fhir-itb

Add traceability #3