SilkTest 16.0: Problems using Timer.startNew() method in Silk4J.

SilkTest 16.0: Problems using Timer.startNew() method in Silk4J.

The Silk4J 16.0 documentation states the following in regard to the startNew() method of the new Timer class:

public static Timer startNew()

Initializes a new Timer instance, sets the elapsed time to zero, and starts measuring elapsed time. The name of the timer is TimerXX, where TimerXX is auto-incremented, starting with Timer0. The name is provided for interfacing with Silk Performer.
Returns: A Timer instance that has just begun measuring elapsed time.
 
 
However when a new timer object is declared via this method no timing metrics are generated during test replay, as shown in the following screenshot:
 
 
This behavior is the result of a known issue in Silk Test 16.0, where Timers created via startNew() are not initialized automatically as the documentation suggests. This problem will be addressed in a future version of Silk Test but in the meantime it's possible to workaround the problem by explicitly calling the start() method against the Timer object:
 
 

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:
‎2015-03-04 17:22
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.