You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@adrianth
Now, when calling macro, the call string of this macro in the log is AFTER all the actions that are performed in this macro, which is extremely inconvenient.
Example:
Macro open github.com MyTest.yaml:
- description: Open gihub pagemacro: OpenGithub
OpenGithub.yaml:
description: Open gihub main pageactions:
- description: Open gihub main pageaction: org.getopentest.selenium.NavigateToargs:
url: https://gihub.com
As a result, first the action of Open gihub main page will be in the log, and only then the line with the Macro: Open gihub page.
Like this:
Actor
Action Description
Duration
Seg.
Result
WEB
Open gihub main page
500 ms
1
pased
WEB
Macro: Open gihub page
510 ms
1
pased
In small macros, this is not terrible, but in large ones that cause other macros, this already creates a huge confusion.
I would like to have the following two entries in the log: Start Macro: <description> Finish Macro: <description>
Like this:
Actor
Action Description
Duration
Seg.
Result
WEB
Start Macro: Open gihub page
0 ms
1
pased
WEB
Open gihub main page
500 ms
1
pased
WEB
Finish Macro: Open gihub page
510 ms
1
pased
The text was updated successfully, but these errors were encountered:
@adrianth
Now, when calling macro, the call string of this macro in the log is AFTER all the actions that are performed in this macro, which is extremely inconvenient.
Example:
Macro open github.com
MyTest.yaml
:OpenGithub.yaml
:As a result, first the action of
Open gihub main page
will be in the log, and only then the line with theMacro: Open gihub page
.Like this:
In small macros, this is not terrible, but in large ones that cause other macros, this already creates a huge confusion.
I would like to have the following two entries in the log:
Start Macro: <description>
Finish Macro: <description>
Like this:
The text was updated successfully, but these errors were encountered: