Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..
387 views

How to diagnose TruClient-Vusers stopping with status "Done. Failed"?

Jump to solution

(LR 12.53 / TruClient / Win 7 SP1)

In one of our screnarios (with each group running for 1 hour) some TruClient Vusers are stopping with the status "Done. Failed." earlier than the 1 hour scenario duration. The corresponding Vuser's log doesn't contain any reason for the early termination of the script.

Screenshot LR Controller Scenario with stopped Vusers.png

Now I'm wondering how to diagnose this issue?

Cheers,

Thomas

0 Likes
1 Solution

Accepted Solutions
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: How to diagnose TruClient-Vusers stopping with status "Done. Failed"?

Jump to solution

Hi Thomas,

In all cases there were errors in the Vuser log indicating about different issues. one time an object was not found, in another case Verify object step failed in the last one navigation step failed.

I suggest to troubleshoot that by running the script in interactive mode for 20 iterations or so and make sure the script knows how to deal with application failures. 

When an object is not found in most cases it is an application issue (slow page loading or wrong\different page was loaded). You can either try reloading the page in the script or add a Wait for object in a loop to make the script more tolerant for slower response time.

Regards,

Shlomi

 

View solution in original post

4 Replies
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: How to diagnose TruClient-Vusers stopping with status "Done. Failed"?

Jump to solution

Hello Thomas,

Thank you for your post.

Based on the screenshots that you shared, I can see an error which could be a clue of this behaviour.

The error says: Target object was not found.

Something that you need to consider when you work with TruClient scripts, before to run the controller, you need to be sure that the  TruClient script works fine without issues on VuGen from Load Mode and on Develop Mode. As this kind of error messages occurs during the replay of the script. If you find this same error message on the script, please refer to the attached guide, where you are going to find how to hanlde this kind of behaviours

 

Regards,

Daniela Gómez Alvarado
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: How to diagnose TruClient-Vusers stopping with status "Done. Failed"?

Jump to solution

Hi Daniela,

thanks for the pointer.

These "Target object was not found" errors occured because the SUT was saturated.

In the scripts runtime setting was selected "Action on error: Continue to the next iteration". So I was expecting that the Vuser is ignoring these kind of errors.

How can this behavior (ignoring any error and continuing with the next iteration) be achieved with TruClient scripts?

Cheers,

Thomas

0 Likes
Highlighted
Trusted Contributor.. Trusted Contributor..
Trusted Contributor..

Re: How to diagnose TruClient-Vusers stopping with status "Done. Failed"?

Jump to solution

The following screenshot shows the logs of other failed Vusers (no "target object not found" involved here):

Screenshot LR Controller Scenario with other failed Vusers.png

 

Does this mean that we have to add a surrounding try block in every TC script?  =8-o

Cheers,

Thomas

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: How to diagnose TruClient-Vusers stopping with status "Done. Failed"?

Jump to solution

Hi Thomas,

In all cases there were errors in the Vuser log indicating about different issues. one time an object was not found, in another case Verify object step failed in the last one navigation step failed.

I suggest to troubleshoot that by running the script in interactive mode for 20 iterations or so and make sure the script knows how to deal with application failures. 

When an object is not found in most cases it is an application issue (slow page loading or wrong\different page was loaded). You can either try reloading the page in the script or add a Wait for object in a loop to make the script more tolerant for slower response time.

Regards,

Shlomi

 

View solution in original post

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.