Page 1 of 1

Delta of Requirements in Test Plan and All Requirements

Posted: Sat Jun 13, 2015 8:32 pm
by devonk
Hi,

At my project we have a Test Plan for an upcoming SDK release. We're using the Requirements-based report to see which requirements are being tested.
Is there a way to quickly see if a requirements is being checked or "active" in a test plan?
What we wanted was a list of requirements that were NOT being tested in the current Test Plan. With that list we could go over them to make sure we didn't forget to add tests to this test plan for a requirement we really needed for the SDK.

I wrote a python script that accepts the exported xml of all requirements and an html source of the req based report frame and creates a list of deltas for me. If people want I can share the script here.

Curious if I'm overlooking something or the functionality is not considered or not yet implemented.

Re: Delta of Requirements in Test Plan and All Requirements

Posted: Sun Jun 14, 2015 9:29 am
by fman
if you have something to share, do no ask just share it.
Best way

create repo on Githib and provide link here

Test plan are made of Test Case Versions, and you can specify a relation/dependency between Test Case <-> Requirement, then knowing what test cases are in test plan you get what requirements are in test plan.
Then if you mean for delta REQ written for the Test Project and that have a test case related to it assigned to a test plan, you can get this info.
But as usual a clear detailed specification (more than 10 words) with examples, output samples and so on are needed in order to understand
if feature has to be implemented and how.
OpenSource does not means that developers are able to create things with fuzzy requirements.
You and me accept fuzzy req on real life from our customers (with all the problems this create) just because THEY PAY FOR THE WORK.

Re: Delta of Requirements in Test Plan and All Requirements

Posted: Mon Jun 15, 2015 8:31 pm
by devonk
I'll throw it on GitHub some other time, meanwhile here's the code on Pastebin: http://pastebin.com/vuycrLMM

It's quickly whipped together so please don't mind the dirtyness of the code.
It's also not 100% watertight as it seems I have a couple of requirements it says are not in the test plan when, in fact, they are. Not sure why this is the case though as I just compare the docid of the reqs. But at least it's better than the other way around where you'd be missing some.

If you've got any questions about it, let me know.