Quantcast
Channel: LoadRunner Practitioners Forum topics
Viewing all articles
Browse latest Browse all 3978

Is there a workaround for a if-else workflow bug in TruClient?

$
0
0

Working with LoadRunner 12.50 and using TruClient to record scripts, I discovered a probable bug in an if-else workflow. To be precise, I have the following if-else workflow:

 

IfClause.png

In the 'if' step, I am trying to identify an object using descriptors (first red box). Depending on the result, one of the two following steps are being executed.

However, when I click on "Click here to edit" to edit the descriptors of identifying an object in the first red box I can edit e.g. the ID:

 

IfClauseDescriptors.png

But afterwards, also the descriptors for the else-clause (second red box) are being changed accordingly!

Again: When I edit the descriptors of the if-clause, the descriptors of the else-clause change as well. I am not able to change the descriptors of one box seperately! I hope my description is clear...

Is there a workaround of this probably bug? Otherwise I cannot use the if-else clause...?

Is this bug known to the LR team?

 

Additional information: I tried to replace the else-action by a kew function "Generic Object Action", which does not solve my problem. A change for the descriptors in the if-block changes the descriptors in the else-block again...


Viewing all articles
Browse latest Browse all 3978

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>