FatCat
August 10th, 2001, 01:27 PM
Here's my situation. I need to log/capture the time it takes between two distinct points in time. Logging the elapsed time might go something like this...
Step 1
Wait until the user has pressed or clicked "OK" on a login screen then start our elapsed time counter.
Step 2
When a window named "myWindow" exists and the status bar has been created and drawn then Stop the elapsed time counter.
Calculate our elapsed time and store this to a log file
Step 3
IF the status bar doesn't get created within our timeout period then log this as a failure.
The problem I am having is that the the application being tested is unrelated to the logging application and is a completely separate application.
Ideally the logging app would detect the Start event of the sequence ( in this case the user clicking on the Button ) and then the Tested app would cause an event to fire in the logger that stops the elapsed time counter when the status bar has been created on the next window.
any suggestions ?
Step 1
Wait until the user has pressed or clicked "OK" on a login screen then start our elapsed time counter.
Step 2
When a window named "myWindow" exists and the status bar has been created and drawn then Stop the elapsed time counter.
Calculate our elapsed time and store this to a log file
Step 3
IF the status bar doesn't get created within our timeout period then log this as a failure.
The problem I am having is that the the application being tested is unrelated to the logging application and is a completely separate application.
Ideally the logging app would detect the Start event of the sequence ( in this case the user clicking on the Button ) and then the Tested app would cause an event to fire in the logger that stops the elapsed time counter when the status bar has been created on the next window.
any suggestions ?