Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Why is it that in one execution server, the "Time Left" data is displayed and in another there is no data displayed?

Why is it that in one execution server, the "Time Left" data is displayed and in another there is no data displayed?

Problem:

Why is it that in one execution server, the "Time Left" data is displayed and in another there is no data displayed?

Resolution:

QUESTION
----------------------------------

Why is it that in one execution server, the "Time Left" data is displayed and in another there is no data displayed?

ANSWER
----------------------------------

This information pertains to a system which comprises of two remote execution servers.

SilkCentral Test Manager cannot generate a Time Left value for a test which has never run before. Any test must be run at least once in order to generate an overall "run time" value which is then used to calculate the "Time Left" value in subsequent runs.

This means that the overall "run time" of the test on its first scheduled run (on execution server 1) will be used as the baseline (to generate the time left) for any subsequent runs on Executions server 1. This information is not available to generate values on Execution server 2, for it will generate its own values depending on how long it takes to run the test for the first time.

A new baseline will be needed for each execution server, meaning that it will need to be run once on each execution server before a "Time Left" field will be displayed in the activities window.


The above screen shot shows a project in a state of execution, those manual tests which are in a "Pending" state have not been previously executed thus there is no "Time Left" data to be displayed.

However for those non-manual tests which have been previously executed and are in a "Queued" state, a "Time Left" of 0h 0m 0s is displayed. This will be updated to a calculated "Time Left" based upon their previous execution time, when that execution definition moves from a "Queued" to "Active" state.

Old KB# 24727

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 19:48
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.