loadrunner script – siebel web protocol – fails after new build – any suggestions?
Question ID: 104099

After a new build, the script fails – appears to be related to server sending responses inconsistently to match the siebel star array parameters captured during recording. Only solution received so far is to re-record the script which will change the left and/or right boundary of the array or the ord/instance of the array.

Marked as spam
Posted by (Questions: 1, Answers: 0)
Asked on April 23, 2010 7:33 pm
Answers (1)
Private answer

Siebel is a complex environment. There are many places where the scripts use ''system generated names'' such as s_2_1_32. These numbers are subject to change not only with system upgrades but, sometimes, with simple changes to the application.

It is possible to correlate these items to make the script more robust but it will require many manual adjustments to make it work. Over time, there could be more of these adjustments required.

It is frequently necessary to re-record the script. If the new script is ''parallel'' to the old with different field names, then the field names can be adjusted. If, however, the parallelism is not exact, either the script logic must be patched (copy from the new recording to the old) or re-recorded.

Marked as spam
Posted by (Questions: 1, Answers: 5)
Answered on May 5, 2010 4:19 pm

Welcome back to "EyeOnTesting" brought to you by Orasi Software, Inc.

Scroll to Top