When running a Queuing workload, why does the test show a status of finished but no actions are performed?
For example, when running a Queuing workload test, a script may be set to generate virtual user output files. However, when the load test is executed and finishes, no output files are generated. This is because the actions in the code, which should write to the output file are never performed, due to the settings above, but the test appears to execute successfully. This applies to any functions, not just output files.
If you uncheck this setting, or use a simulation time in the workload, then the script will run properly and actions will be performed as normal. To enable/disable this setting, navigate to the following in Silk Performer:
[SETTINGS | ACTIVE PROFILE | REPLAY | SIMULATION | SETTINGS | Stop Virtual User After Simulation Time (Queuing Workload)]