Utility for running robotframework test files in parallel, even without having them being specifically written for it.
MIT License
Utility for tests written using RobotFramework - run test .robot files in parallel even if they are not specifically written for this.
This utility does not aim to replace pabot. It is basically a test executor - just a quick project to be able to execute in parallel previously written RF test run in serial fashion. As such, it only offers three basic options.
For much sophisticated solution, use Pabot.
If you want to simply execute your robotframework test files in parallel fashion, you can use this tool. It leverages multiprocessing package of python, so there is no worry about specifically preparing your tests.
This tool currently supports:
run all .robot files in parallel: python[3] -m parabot -a
run all .robot files in specific folders: python[3] -m parabot -f <relative_path_to_folder_1> ... <relative_path_to_folder_n>.
run tagged tests/suites: python[3] -m parabot -t <tag_1> ... <tag_n>
change default timeout when using parameters -a or -f: python[3] -m parabot -to [int]
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.
What things you need to install the software and how to install them.
Just run [sudo] python[3] setup.py install and it will take care of it for you.
You can either clone this package from the repository, or install it via pip.
In case of cloning, use these steps to install:
Run [sudo] python[3] parabot/setup.py install
You can try the project on the examples tests in the folder examples.
To try it on your project:
3.1 Create a new branch for this, if things get messed up!!!
3.2 Copy parabot folder into the root of your project
3.3. Run [sudo] python[3] parabot/setup.py install
3.4. Run some of currently supported commands
3.5. See what happens :).
In case of using pip:
Run command sudo pip3 install parabot
Then try available commands as described above.
For options -a and -f are timestamped report folders created in the same folder, where .robot file (test suite) is located.
For option -t the timestamped report folders for each tag are created in the reports folder located in the root.