sschwanbeck Contributor.
Contributor.
336 views

What would cause users to complain that the assigned tester fields are blank

Jump to solution

many users are complaining that even though they have entered the assigned tester three or four different times, when they click on a test set and view the execution grid, there is no assigned tester there.  It doesn't happen for all the scripts, but several of them.  They are fixing these blank testers daily and they keep showing up empty?

0 Likes
1 Solution

Accepted Solutions
Highlighted
Knowledge Partner
Knowledge Partner

Re: What would cause users to complain that the assigned tester fields are blank

Jump to solution

 Hi sschwanbeck,

In Default ALM project Test Script fields , there is no such field called "Assigned Tester".

Test Script only has a field called "Designer" which will be populated by user id of whichever user created it.

When this test script is added as a test instance to any test set this field reflects as a "Responsible Tester" having the same test designer id.

May your team is using some customized ALM project in which "Assigned to Tester" is specifically created as a UDF ( user defined field ) in Test Script as User list type.

Ideally when a "user id" is filled in "Assigned To Tester" field in Test script, the same should be propogated to the test instance level as well, value of "Assigned To Tester" field should not get wiped out.

What I am suspecting is, there might be some workflow code running in the background in below 3 event subroutines which is wiping out value in "Assigned To Tester" field  of test instance.

TestSetTests_MoveTo 

TestSetTests_FieldCanChange(FieldName, NewValue)

TestSetTests_FieldChange(FieldName)

Please ask your adminsitrator to verify code in these 3 subroutines to see if there can be any possible corrections.

Regards,Srihari

2 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: What would cause users to complain that the assigned tester fields are blank

Jump to solution

 Hi sschwanbeck,

In Default ALM project Test Script fields , there is no such field called "Assigned Tester".

Test Script only has a field called "Designer" which will be populated by user id of whichever user created it.

When this test script is added as a test instance to any test set this field reflects as a "Responsible Tester" having the same test designer id.

May your team is using some customized ALM project in which "Assigned to Tester" is specifically created as a UDF ( user defined field ) in Test Script as User list type.

Ideally when a "user id" is filled in "Assigned To Tester" field in Test script, the same should be propogated to the test instance level as well, value of "Assigned To Tester" field should not get wiped out.

What I am suspecting is, there might be some workflow code running in the background in below 3 event subroutines which is wiping out value in "Assigned To Tester" field  of test instance.

TestSetTests_MoveTo 

TestSetTests_FieldCanChange(FieldName, NewValue)

TestSetTests_FieldChange(FieldName)

Please ask your adminsitrator to verify code in these 3 subroutines to see if there can be any possible corrections.

Regards,Srihari

sschwanbeck Contributor.
Contributor.

Re: What would cause users to complain that the assigned tester fields are blank

Jump to solution

Thank you very much for your response!  I did look in each of those 3 event subroutines, and while it wasn't there, it did lead me to a new subroutine that an old administrator created.  I made some changes to the code and it seems to have solved the problem!!  Thanks very much!

 

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.