continuous integration - Achieving bi-directional traceability between unit tests and issues, on a CI and JIRA setup -
continuous integration - Achieving bi-directional traceability between unit tests and issues, on a CI and JIRA setup -
i'm trying find way developers produce bi-directional traceability between our nunit test cases , jira issues without going out of way. nunit allows categorize test cases, means we'd able produce traceability categorizing tests ids of issues. allows execution of tests specific issue. i'm not sure if right approach. i'm trying find way developers produce traceability without going out of
we built vivid trace help solve category of problem.
if tasked approach, i'd consider shadowing each nunit test case jira issue, in 1:1 correspondence. zephyr jira, example, comes pre-packaged test issue type , fields, can roll own in jira. after coming mapping scheme identifies each unique nunit test, can automate mapping process using jira's rest api create/manage test cases in jira based on code base of operations reality.
the key utilize jira's issue linking feature link jira issues of concern managed jira test issues, either straight or indirectly. issues linked test issues, vivid trace can heavy lifting traceability. can give testing overview of issue. going further, managing requirements spawned issues , linking together, can tell requirements tested , overall status, , tests test given requirement ("originating requirements"). can tell same implementations.
you can more of thought testing automation side considering how might solve situation using zephyr jira along zapi.
(disclaimer: create vivid trace)
unit-testing continuous-integration jira traceability
Comments
Post a Comment