Storing screenshots as files is often not desired in the use-cases of the company I am working at.
We generally prefer having the screenshots embedded into the log files themselves as base64 encoded strings. This may enlarge the log files themselves, but it is much easier to exchange the log files, without consideration of file paths and similar.
In our Remote Library Interface, all screenshot functionalities use Base64 encoded images for logging instead of storing files.
Storing screenshots as files is often not desired in the use-cases of the company I am working at.
We generally prefer having the screenshots embedded into the log files themselves as base64 encoded strings. This may enlarge the log files themselves, but it is much easier to exchange the log files, without consideration of file paths and similar.
In our Remote Library Interface, all screenshot functionalities use Base64 encoded images for logging instead of storing files.
I am already working on a PR to implement this functionality into this library in my fork: https://github.com/HackXIt/robotframework-flaui