Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Vice Admiral
Vice Admiral
619 views

Customization Request - Req ID field

Under Requirements Tab in QC, there is a field labelled “Req ID” which lists down all the test requirements.

 

Is it possible to make this field available in Test Lab tab as well since we need to report test execution based on the requirements covered?

 

I know using SQL code i can get this report prepared.

Thank you...
0 Likes
8 Replies
Absent Member.. Absent Member..
Absent Member..

Is your goal to get a report or to show the field somewhere in the Test Lab module? The suggested solution would be different depending on your goal.
[If this post solves or helps solve your issue, mark the thread as solved and give KUDOS to the author for their assistance.]

(Opinions expressed in my postings are mine alone, and do not reflect the opinions of my employer.No warranties express or implied for any solution/suggestion posted.)
0 Likes
Vice Admiral
Vice Admiral

To show the field somewhere in the Test Lab module they have some different format of reports so they want that field there,

 

Also  i know how i can get this for reporting, Report can be generated from excel report, i have SQL code.

Thank you...
0 Likes
Absent Member.. Absent Member..
Absent Member..

Since Requirements are linked to Test Cases, the association in the Test Lab would be through the Test Instances.

The linked Requirement ID is not directly available from the Test Instance. The only way to get the data for display in the Test Lab would be to create a user defined field for the Test Instance entity and then write custom workflow code to populate the field with the linked Requirement ID.

This could be complicated if you link a test to more than one requirement, or a requirement to more than one test.
[If this post solves or helps solve your issue, mark the thread as solved and give KUDOS to the author for their assistance.]

(Opinions expressed in my postings are mine alone, and do not reflect the opinions of my employer.No warranties express or implied for any solution/suggestion posted.)
0 Likes
Vice Admiral
Vice Admiral

Thanks for the Complete detail,let me try this way and show it to my users, can i have a sample work flow if its handy for you ?
Thank you...
0 Likes
Absent Member.. Absent Member..
Absent Member..

I don't have any sample code to give you.

The Administrator Guide has many examples of workflow customization for various tasks. There won't be anything that exactly matches your need, but you should start learning about workflow customization by studying that document.
[If this post solves or helps solve your issue, mark the thread as solved and give KUDOS to the author for their assistance.]

(Opinions expressed in my postings are mine alone, and do not reflect the opinions of my employer.No warranties express or implied for any solution/suggestion posted.)
0 Likes
Vice Admiral
Vice Admiral

Hmm, are you sure that it can be achieved in v11 ? because in many of the other posts i could see every one stopped in middle.

Thank you...
0 Likes
Fleet Admiral
Fleet Admiral

customization can be done on no consideration of the versions.

 

Some where in past threads i have seen few user fields linking in different module system fields.

those samples may not reach you exactly, just patch up some lines and you will be filled up.

(If this helped, accept as solution )
(Posts and opinions made here are my own and do not reflect the opinions of my employer)
0 Likes
Absent Member.. Absent Member..
Absent Member..

I suspect the reason there is no published solution is because this is extremely complicated to implement correctly. There are many ways the data can be changed, and many places where you need to put triggers to ensure you are displaying current data.

For instance, you of course can't display an associated requirement for a test instance until the test instance is created. So, in the process of creating a test instance you need to catch that action and create custom code to
- trace back to the original test case
- from there figure out the linked Requirement.
To do that requires use of the OTA API within the workflow code. But also consider that there may be more than one linked requirement. And more than one way to create a test instance. You can add a single test to a test set. You can add a whole folder's (or hierarchy of folders) collection of tests to a test set. You can create test instances by copying an existing test set.

Next, consider that the link between a test and a requirement can be severed after the test instance is created. In that case, you need to capture that action and right custom workflow code to
- Find all test instances associated with the test
- remove the Requirement info from the test instance

Next, consider that a link between a test and a requirement can be added after the test instance is created. In that case, you need to capture that action and right custom workflow code to
- Find all test instances associated with the test
- add the Requirement info to the test instances

Next consider that those links can be added/removed when you are in the Test Plan module or the Requirements module. So there are multiple places where you may have to capture the action.
[If this post solves or helps solve your issue, mark the thread as solved and give KUDOS to the author for their assistance.]

(Opinions expressed in my postings are mine alone, and do not reflect the opinions of my employer.No warranties express or implied for any solution/suggestion posted.)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.