Continuous Integration

Automa is very well suited for continuous integration. In fact, Automa's own build is part of a continuous integration infrastructure that automatically runs a near-complete regression test after each committed source code change, and makes it possible to release a new version of Automa at the click of a button.

Integrating an Automa script into a continuous integration process can be done in two ways. Both rely on running Automa scripts from the command line, which all continuous integration systems support.

To execute an Automa .at file that was created using Automa's save() function, you simply open that file with Automa.exe. More precisely, if your copy of Automa.exe lies in c:\Program Files (x86)\Automa.exe and the .at script you want to run is c:\dev\tests.at, then you can integrate this step into your continuous integration system as the shell command

"c:\Program Files (x86)\Automa.exe" c:\dev\tests.at

To test that this works, you can paste the above line into the Windows command prompt.

The second way of integrating Automa into a CI system applies when you are using Automa as a Python library. In this case, you use the python.exe binary from your Python distribution instead of Automa.exe from above. For example, let's say you installed Python into the default location c:\Python27 and the Python/Automa script you want to execute is c:\dev\tests.py. If you are using the .zip version of Automa (see our download page) and have unzipped Automa to, say, c:\Program Files (x86)\Automa 1.4.7, then you need to add c:\Program Files (x86)\Automa 1.4.7\library.zip to your PYTHONPATH environment variable:

PYTHONPATH=%PYTHONPATH%;c:\Program Files (x86)\Automa 1.4.7\library.zip

Once the environment variable is set, you can execute your script via the shell command

c:\Python27\python.exe c:\dev\tests.py

If you have problems following the above steps, please don't hesitate to get in touch on our contact page.