A package can be run on the selected agents, or on all available agents allowed by the package’s definition
An agent is available when is not offline and is not disabled. In case an agent runs another package is still seen as an available one. Each agent keeps internally a queue(FIFO) with the requests packages to run. This requests can be canceled at any time by the initiator, but for now, there is no way to reorder the packages that are waiting in the queue on an agent.
When a package runs on multiple agents, Korredo will create a list of tests from all configured assemblies and this list is split evenly across that agents.read more
A package step represents the most important part of a package. It has a name which should be unique and depending on the step’s type, the user can configure specific information.
Steps are executed in the order defined on package level and it can be configured to stop execution in case any of the steps exists with a code different than 0.
The user can also disable a step or reorder the steps. In the step definition form, the user can use a series of parameters called environment and system parameters. The environment parameters can be edited by going to the Settings forms and adding values to the form located on the bottom. For more details please check the Transforming parameters section.
A package allows you to run commands, scripts and tests on your agents. To get started, click on the New package link from the Test Runner tab:
Before creating a package you might want to add some environment parameters, as a connection string, a TCP port or a specific disk path. For more details please read Package parameters
1. Package directories
The first step is to add directories to your package. Each directory you select will be recursively copied to the package. For an easy use, each directory will be given an alias so that you can use it in other places (for BAT/EXE parameters, bash scripts …)
For example, if you add the directory c:\project1, then it will get the alias F0. This folder can be used using the parameter %alias.F0%read more
A package is a collection of directories, assemblies, scripts, and steps. A step can be configured to run a command file/exe, a script or a test runner (Nunit or Visual Test Console).
Once a package was defined, Korredo keeps its definition on disk under the Packages folder. The packages can be modified, copied or deleted at any time.
Using the definition from a package level, Korredo creates an archive file with the specified directories. This archive is then sent to all available agents and each agent executes the package based on the defined scripts and steps. In the end, the result of a package is sent back to the requester as a collection of artifact files.read more