If you have a lot of integration tests that take a significant amount of time to run, then Korredo comes in handy. Before actually committing the source code, you can run your tests on other machines while you can continue working on something else.
Depending on how many agents are installed, Korredo will split the tests evenly and will run them in parallel. As soon as a test is run, you will have feedback and see in real-time what is failing and with what exceptions. Before using Korredo, you must compile your source files/project(s).
What does Korredo behind the scene:
- Copies the folder(s) the user configures to the packages folder inside Korredo.
- Creates a list of tests by scanning the assembly files configured by user.
- Using the above list assigns evenly a sublist of tests for each available and selected agent
- Creates an archive with the above package (this archive contains one or more folders, assembly files, executables, and other resources)
- Sends the archive to all selected agents (in parallel) and enqueue the package to the each agent’s queue for execution
- Runs the steps you configured on package level (including the step to run tests) on each agent.
- Receives feedback in real time about running tests from agents
- Receives output in real time about each step from agents.
- Receive artifacts from agents when a build finishes.
A short demonstration of running tests in parallel on two agents using the wizard:
Supported test runners:
- Nunit 2.X
- Nunit 3.X
- MS Test (or VS Test Console 2015 and 2017)
Besides these runners, Korredo supports also the following step types: custom scripts, command and text replace.
- Chat: with rooms, capture desktop and send images, emoticons, search. No accounts are necessary
- Checklist: create/edit checklists with images, shared across a team, with notifications when items are added/removed
No server or database installation is required.
Two executables are part of the Korredo installer: Korredo.App.exe and Korredo.WindowsService.exe. The first one is the GUI and the second one is the windows service for agents. The GUI app can run packages initiated by other GUI apps.
Screenshot from Korredo: