How to transfer visual UI testing macros to another machine

We have encountered one issue while exporting the macros and running on the other machine.

Actually we have created a macro, which will perform the desktop automation like Open Remote Desktop application and open web browser. For that we have used “XClick” as one of the function where it stores the screenshot images. But when we export that macro to an HTML file and try to execute it on different machine, it troughs an error. When we investigated, we found that there are no images that we have captured during the macro creation.

Are we missing any point/step as a part of export macro activity ?

Currently, to transfer a macro that uses images, you need to export the images manually or use the backup feature to export all macros (the backup includes the images!).

With the next update, in addition to the current JSON macro export option, you will have the option to export macro plus all images used by this macro at once. All will be a single ZIP file macro that you can easily import on any other machine.

Actually, I recommend that you use the hard drive storage mode, then all images are directly on the hard drive, and you can just copy them to the new machine:

Starting with V5.6.5 the ZIP import/export feature is available!

Export macros with everything: Macro, images, CSV and even subroutines (RUN command) all inside a ZIP file:


Import macros directly at the folder level. Images, CSV and subroutines are imported as well:


Current version available on Chrome web store is 5.5.7 which not include this functionnality, did you know where it will be released? (in firefox store it’s ok)

The Chrome Store publishing delays have become very long. It is a common complaint around extension developers in the last weeks. So we are really not sure when it will be published. My personal guess is in 1-2 weeks.

Meanwhile the Firefox and Edge (based on Chromium!) versions are available.

You could always export the JSON, and the whole images folder.
In the other machine, you import the JSON again, and import each image at a time.
In the origin:

In the destination: