[3.1.0] Add "Flow" keyframes/output to console log in stead of incorrect statement #23
Description
Current console ( Statement does not make sense as it indicate that we are waiting, but we actually have a schedule running ):
Schedule xxx_dk--xxx_dk--smoketest[e6683b12-2ddb-4b9b-853f-c4fa18908e3b] Launched Successfully!
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
The schedule status is already 'Executing' - wait a minute...
|---------------------------------------------------------------
Schedule: xxx_dk--xxx_dk--smoketest[e6683b12-2ddb-4b9b-853f-c4fa18908e3b]
"wait a minute" is actually the configured delay and not a minute. That is too "noisy"..
Output from 3.0.0 - style: ( desired - could be an option)
Schedule xxx.dk smoketest - afviklermaskine - xxx.dk[e6683b12-2ddb-4b9b-853f-c4fa18908e3b] Launched Successfully!
RunId: '313a09d7-3980-4b7c-a104-920e702e748d' is not ready yet - wait a minute
RunId: '313a09d7-3980-4b7c-a104-920e702e748d' is ready to monitor
----------------------------------------------------------------------------------------
RunItem: TTS-543 NB søgeboks på xxx.dk forside | Status: Passed | Elapsed: 29.1261534
2018-11-19T12:59:04.0221219+00:00 - Scheduled run executed from schedule 'xxx.dk smoketest - afviklermaskine - xxx.dk'
2018-11-19T12:59:04.0688448+00:00 - Connecting to Azure agent
2018-11-19T12:59:04.0688448+00:00 - Connected to Azure agent with size 1024x768
2018-11-19T12:59:04.240719+00:00 - Running
2018-11-19T12:59:04.871487+00:00 - Variable 'URL' was loaded with value 'xxx.dk'.
2018-11-19T12:59:09.320793+00:00 - Chrome was successfully started.
2018-11-19T12:59:17.7958832+00:00 - Chrome loaded url xxx.dk
2018-11-19T12:59:17.9208823+00:00 - Looping, current value is 1.
2018-11-19T12:59:31.171265+00:00 - Web element was not found within 10 seconds
2018-11-19T12:59:31.171265+00:00 - Breaking current iteration scope.
2018-11-19T12:59:31.1877461+00:00 - Loop is broken.
2018-11-19T12:59:31.7033066+00:00 - Left-clicked on web element 'A' at position 821:602
2018-11-19T12:59:31.9411172+00:00 - Left-clicked on web element 'DIV' at position 164:90
2018-11-19T12:59:32.2001211+00:00 - Found web element 'A' at position 194:397
2018-11-19T12:59:33.2013336+00:00 - Case is passed.
Environment: Azure agent
- It helps debugging and comparing flow execution out from run to run.. In the current implementation it is not possible to see how a good run trace output. Only failures available in LeapWork. In LeapWork it is not possible to find runs by id's etc..
- It helps understanding progress without opening LeapWork Studio