Sunteți pe pagina 1din 2

http://www.croutonsoflife.

com/automation/silk-performer/recursive-link-checker-o
r-web-crawler

http://kb.microfocus.com/display/4/kb/article.aspx?aid=19393&n=1&docid=8705819&t
ab=search
http://kb.microfocus.com/display/4/kb/article.aspx?aid=19787&n=1&docid=8706236&t
ab=search
===========================================================
http://kb.microfocus.com/display/4/kb/article.aspx?aid=17666&n=1&docid=8704004&t
ab=search
Why when I use the Halt statement in my script does the "End" transaction still
get called?
Resolution:
ANSWER
----------------------------------
This is a known issue and is planned to be fixed in a future release. It only ha
ppens when you have specified the "Call end transaction for stopped virtual user
s" option in the active profile. As a workaround call the SetCallEndTransaction
function prior to the Halt statement in the script. For example:
SetCallEndTransaction(false);
halt;
===========================================================
Is it possible to exit a Function but continue executing the Transaction?
Problem:
Is it possible to exit a Function but continue executing the Transaction?
Resolution:
There is no SilkPerformer function that can be used to exit / stop a function in
the middle of it"s execution and continue executing the transaction. The closes
t is the THROW function, however this is only allowed in event handler functions
.
Some of SilkPerformer"s control statements include:
HALT: Terminates the simulation of a virtual user.
RETURN: Terminate the execution of the transaction
EXIT: Terminates the loop (while, for, or loop) in which it is directly nested.
THROW: Terminates the execution of an event handler function by passing executio
n control to the runtime system. The runtime system continues with the default p
rocedure for the event.
The throw keyword is only allowed in event handler functions. If the throw seman
tics is not applicable in a handler when called as a function, it finishes handl
er code execution.
========================
Why is the transaction count defined in BDL script not effective during the load
test?
Resolution:
QUESTION
----------------------------------
When running a load test, you may notice that the transaction number of times th
e transaction was repeated was not as defined in the BDL script:
Script:
..
dcluser
user
VUser
transactions
TInit : begin;
TMain1 : 2; //TMain1 is defined to be repeated 2 times
TAgain : 1;
..

During load test, was noticed to have repeated 9 times:


ANSWER
----------------------------------
The script defined value is only effective for Queuing workload model. For the o
ther workload models, the transactions are required to loop so as to meet the de
fined simulation time, or when the test simulation is stopped. The scripted valu
e will define the pattern that is followed, i.e. in the above scenario TMain wil
l execute 2 times, and then TAgain will execute once, before the pattern is repe
ated again.
To ensure that the transaction have a fixed repetition regardless of the Workloa
d model chosen, a loop can be defined within the transaction and when the repeti
tion count is reached, perform a "return 2" or "halt" to stop the user simulatio
n
Note:
- "return 2" and "halt" functions will terminate the user simulation immediately
without executing the end transaction.
- Looping within a transaction will not increment the transaction counter in mon
itor, and test results.
==============================================

http://kb.microfocus.com/searchResultpage.aspx?stext=stop+transaction&st=1&kb=&c
at=&subcat=&att=&remotesite=