Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

What are the generated files (.js .log .raw) after running an automation flow? #147

Closed
kensoh opened this issue Apr 28, 2018 · 1 comment
Closed

What are the generated files (.js .log .raw) after running an automation flow? #147

kensoh opened this issue Apr 28, 2018 · 1 comment
Labels
query

Comments

@kensoh
Copy link
Member

kensoh commented Apr 28, 2018 •
edited
Loading

What are the generated files (.js .log .raw) after running an automation flow?
@kensoh kensoh added the query label Apr 28, 2018
kensoh added a commit that referenced this issue Apr 28, 2018
@kensoh
#147 - add readme note on generated .raw file
c516af2
@kensoh
Copy link
Member Author

kensoh commented Apr 28, 2018

On running an automation flow, a .raw file is created to store contents of expanded automation steps. The tagui step can be used to call other automation files to be run within an existing automation. The .raw file helps in debugging to cross-check error messages with the full automation sequence.

The .js file is the generated JavaScript file that contains lines and lines of executable and working JS code that drives the UI automations through web-browser, Sikuli, or other integrations.

The .log file is a log that saves output of the execution for record or reference purposes.

@kensoh kensoh closed this as completed Apr 28, 2018
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
query
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kensoh