How can I tell if a test was stopped, killed or aborted after a test has been run?

How can I tell if a test was stopped, killed or aborted after a test has been run?

You can tell whether or not a load test was stopped, killed or aborted by referring to the information stored in the repository for the test.  An SQL query statement, as detailed below, can be formed to reveal how the test was terminated, where Perf_agent_ugrp is a table in the Silk Performer repository database:

select count(*) from perf_agent_ugrp where pk_loadtest = xxx

If the result is 0, then the test was either aborted or killed. There is no way to distinguish between Abort or Kill states from the database.

select count(*) from perf_agent_ugrp where (pk_loadtest = xxx) AND (userca > 0)

If the result is 0, then the test was terminated with a Stop state.

For a definition of the differences between the Stop, Kill and Abort termination types, please see the following resolution: Stop, Kill and Abort .

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:47
Updated by:
 
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.