As a developer, you have sometimes to follow a series of rules, especially when it’s about the user interface. For this kind of situations, Korredo can help you to define checklists with title, description, and image.
The checklist tab has 3 zones
Left area: contains the checklists
Middle area: contains the items for the selected checklist (each item has a checkbox)
Right area: contains the description and image for the selected item
In order to have support for these checklists, you must install the following php scripts to an Apache server:
savefile.php – contains the logic to save checklists
upload.php – contains the logic to upload image files for a checklist item
checklists.txt – the file that stores the checklist names (this files needs write permissions for Apache)
The URL where these files are installed needs to be properly configured in the Settings form, the field Site URL (no ending / is required)
Add a new checklist
To add a new checklist, access the contextual menu in the left pane, and select New checklist. You will be prompted to enter the name. After the name is introduced, a new text file will be created at the Site URL address (from settings).read more
The Korredo agents run as a windows service and can be installed by running the install-service.bat from the root folder. The agent allows you to run packages in the same way as running them using the GUI app.
The agent uses the same config file for environment parameters: agent.config.txt
The GUI and the agent cannot correctly run at the same time.
If Korredo runs as a windows service, can be restarted from other GUI applications by accessing the contextual menu from the Agents grid:
Restart agent: it will restart the agent in case something remains hanged.
By default, all users defined in the Known hosts table are part of the #Team room. New custom rooms can be created by entering a text in the drop-down below and pressing ENTER, but all users will be part of it:
A new room with custom users can be created by selecting the users from the left grid and pressing the New button. In this case, the room name cannot be configured.
To access the conversation history of a room with custom users you need to recreate again that room by selecting the same users.
Korredo has a basic chat functionality with the following features:
No user account is needed (but friendly names for users can be configured)
Capture desktop screenshots and sending them very easily to interlocutors
Basic image editor for screenshots with the possibility to add arrows, rectangles, and text
Search through past conversation
Buble notifications when Korredo is minimized.
Flash of Korredo window when is not on top and a message is received.
Offline messages (Apache server required)
Each user gets a different color
Multiple conversations supported in parallel using tabs
Check marks for each message, similar with what’s up: message sent, seen, sent as offline, failed to send.
The idea of the chat plugin is to have a simple way of communication between team members with an easy way of sending screenshots with basic editing(arrows, text). The entire communication is based on machine names.
In order to have support for online messages, the scripts from the PHP folder should be copied to an Apache server. Then the server URL should be configured in settings. The following PHP files are required by the chat plugin for the offline functionality:
getchat.php – gets the offline messages from a specific user (after the offline message is fetched, it will be deleted)
getchats.php – gets the list of users that left offline messages for the current user.
savechat.php – saves an offline message in a file.
The conversation can be cleared at any time and they are stored in the Conversations folder in plain text. Please note that the offline messages are kept in files in the Apache server and anyone can read them. There is no encryption mechanism and no sensible data should be transmitted using the chat.read more
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
The NUnit runners are part of the Korredo installation package. The VS Test console Agent needs to be downloaded & installed separately. This can be done by opening the Korredo as an administrator and accessing the menu Options->Settings. The admin privileges are required because the plugins need to be copied into the VS Test console path under Program Files directory.
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