Health Check Tool

Gone are the days of endless, back-and-forth emails and conversations between customers and Customer Support in attempts to validate that the computer is ready for installation of the RPA server. Although communication is still critical before installation, validating that the computer is ready, the ports are open, the memory and CPU is sufficient, and so on; just became so much easier. We created a Health Check Tool, to ease and shorten installation and upgrade by helping you validate that all prerequisite requirements are met.

Be sure to check all system requirements prior to installation.

The Health Check Tool is simple to install and is comprised of only two parts:

  1. EXE file

  2. JSON file

This testing tool can be performed in-person by Customer Support before installation; or you can simply do the test on your own.

The test is separated in categories:

  • Connectivity

  • Database

  • Hardware

  • Software

Under each category, there are several checkups that are performed. You have the option of selecting which will be done, by checking or unchecking the boxes. Once your choice selections have been made, you will be able to see how many checkups will be performed by looking at the listed number.

Upon test completion, a Test Summary output will be created.

This output can be exported in PDF, Excel, or JSON format from the Export button on the upper right side. This enables you to easily share the test results with Customer Support, or to an IT professional who is aiding in the installation or upgrade.

Additionally, besides for the Test Summary, a full list of Test Details are available for completed tests. They are designed to be as specific as possible for error descriptions.

The following is the definitive order that the test tool uses when assigning the run-time values of test input parameters. The highest precedence is listed first:

  1. UI configuration - Values might be manually set on the UI side by the user.

  2. File configuration - Values from appconfig.json configuration file.

  3. Default value - Any given test parameter may have a default value defined by a developer.

Customer Support, or users, have the option to configure the test according to their needs. The value of the input parameters can be changed on the UI side, but this will not overwrite the original JSON file.

To change the configuration settings on the UI side:

  1. Download the Health Check Tool executable file. Click here to download.

  2. In the Download folder, run the Kryon.Environment.Test.Tool.UI.exe.

  3. The testing tool opens.

  4. Click Configure to change the value of specific input parameters.

  5. Some are filled by default, others are left blank to accommodate different customer environments.

JSON File Configuration

Users with advanced knowledge, or Customer Support, can edit the JSON file.

To configure the input parameters in the JSON file:

  1. In the Download folder, open the appsettings.json file.

The Configuration section "TestSettings" contains the following properties:

Name

Description

RunInParallel

  • Optional

  • Type: Boolean

  • Defines whether to run tests in parallel or sequential

  • Default: False

TestSources

  • Required

  • Type: List

  • List of assembly names that contain test implementations

TestSuite

  • Required

  • Type: List

  • Defines the list of test configurations to run

  • The order in which test are configured is the execution order

Each test configuration contains the following properties:

Name

Description

Id

  • Required

  • Type: String

  • Defines the unique identifier of the test. Currently, it equals the test type defined in the assembly

  • Default: False

Parameters

  • Required

  • Type: Object

  • Defines the input parameters of each test