The home page of Gazelle Test Management can be customized for your needs. This page is made of two main frames, one is first populated with informations coming from the database and you can edit the rest, the other one, can be displayed only if you need it, above or below the first one; and you are totally free to define its content.

From the home page, "Edit" button are available in the panel headers to edit the title. The ones available at the bottom of the panels are for editing the content. The "Move panel to the botoom/top" button can be used to change the location of this panel.

When you edit a title or a panel content, do not forget to hit the "Save" button.

The configuration of gazelle TM is done throught the menu Administration --> Application Preferences

This page contains multiple sections allowing to configure the different behaviors and modules of gazelle.

Application mode

This section allows to configure the different modes of the gazelle TM application.

Gazelle TM can be configured into three modes, and four configurations:

1. Master Model: gazelle act as editor of profiles, samples, and tests plan (example GMM: gazelle.ihe.net/GMM/)
2. Test management (for a Connectathon): used when gazelle act as manager of CAT testing sessions
3. Product registry (store integration statements): gazelle used in this mode to store the integration statements

Gazelle can act as

1. Master Model
2. Test Management
3. Master Model and Test Management
4. Product Registry

Any other configuration will make gazelle out of use

Application settings

This section allows to configure the different administration properties of gazelle TM, which are:

• Application URL: the URL to gazelle application (example: http://gazelle.ihe.net/EU-CAT/). This attribute is used to create permanent links into the application to the test plan, test instances, etc
• Application OID: the unique identifier of gazelle instance (example: 1.3.6.1.4.1.12559.11.1.5). This element is used to create permanent identifiers into the application
• Application URL basename: the base name of gazelle TM instance (example: EU-CAT)
• Application Name: the name of gazelle instance (example: gazelle)
• Admin Name: the administrator's name
• Admin title: the fonction of the admin
• Admin Email
• History Account Email
• Documentation URL: the URL to the documentation of gazelle
• Issue Tracker URL: the URL to the jira tool
• Release Notes URL: URL to release note
• Zone: example : EUROPE
• Google Analytics Code: the identifier of GCA
• Default test language: the default language of test plan descriptions
• Default color: the default skin of the tool   
• Session timeout (in minutes)
• Ping frequency (s): the frequency to update the status of sessions (example : 30)

Messages

This section describes the ability to uses messages modules into gazelle. When allowed, the monitors and the vendors are notified of the status and changes into their test instances.

Assertions

Allows to show or to hide assertions link to a test. This sections is linked to assertion manager via the property 'Assertion Manager rest api url' (example: http://gazelle.ihe.net/AssertionManagerGui/rest/)

CAS - Central Authentication Service

This section allows to link the gazelle TM to a cas service, or to use local database of the TM tool.

Deploy section

The deploy section allows to schedule deployment of gazelle TM ear into a jboss server. This section contains 4 elements:

1. Auto deploy scheduled 
2. Deploy source   : the path to the ear to be deployed
3. Deploy target: the path to the ear in the jboss server
4. next schedule : the next time of deploying

Cache section

Allows to reset the cache used with gazelle (for developers, the cache used is ehCache).

Jira

Allows to link gazelle TM to the jira used, and then vendors can report problems encountered in tests descriptions or test steps.

Avaiable attributes:

• Display jira issues related to test        
• Jira base url        
• Jira Projects keys to fetch issues from: List of project keys (comma separated) that store test issues
• jira Project key to Report issues : Test issues will be reported in this project

Security

This section allows to describes the differents http security attributes related to gazelle.

New features added to improve the security of applications developed by IHE-Europe
The audit security was done by two external teams.
Improvement added :

• CSRF (cross site request forgery)
• SQL injection filter
• HTTP Headers security enforcement
• Better cookies management

MESA tests

This section allows to configure the behavior of pre-cat tests : automatic validation and mail notification

Certificates

Provides a link to the TLS tool

External Validation Service Front-end

Provides a link to EVSClient tool

Auto update section

 This section describe a module in gazelle allowing to update the relationship between Results of testing session, and the systems participating. This section contains two attribtues:

1. Auto update CAT results : this section shall be selected during testing session registration and execution, no need to it otherwise
2. Test Result Refresh Interval (s): the interval of updates

Proxy

This section describes the proxy tool informations

TLS Section

Link to the Client simulator related to gazelle

QR Codes

used for communication between the monitorApp and the gazelle TM. Each TestInstance is described then by a DR codes, which used later by the monitorApp.

DDS - Demographic Data Server

Link to the DDS tool.

Order Manager section

Link to order manager tool

Files/Paths Management 

List of path files used by gazelle TM in the server.

The admin can manae user registration, for all the companies, vendor_admin can do so for users registred for his company.

To do so, the admin shall go to menu -> Administration -> Manage -> manage users

The GUI of the users administration page looks like this:

The admin has the possibility to filter users by

• Organization
• Firstname
• active users
• role of users
• username
• lastname
• blocked or not blocked users

The table that show the list of users contains the following information:

Organization keyword

• username
• name
• activated
• blocked
• number of logins
• last login date
• last modifier username
• the roles affected

The administrator is able to

• create new user
• edit old users
• view information of a user
• connect as a user !
• disable user account : the delete act as 'block', the user is not really deleted from the database

Add users

To add user the admin shall click on the button 'add user'

The page of adding user contains this information:

• The name of the organisation the user belongs to
• firstname
• lastname
• email (shall be a valid mail, and so the user can activate it, and the reset his password, etc)
• username
• blocked?
• account activated
• the list of role attributed:

The following table describe what a user can do and cannot do:

Edit users

To edit a user, you have to click on the button

The edit page contains the same information as the add user page, with the possibility to change the password for a user, using the button "change password"

View users

To view user information, admin shall click on the button

The information provided are the same as in the edition mode

View user preference

The admin is able to view the user preferences, regarding gazelle use, which are:

• Username
• firstname
• last name
• email
• organization
• skype account
• table label : the table used in a current testing session CAT
• show sequence diagram: this enable or disable the use of sequence diagram under test plan and test instances, may be important for performance issues
• Display your email address to everybody ? : for security issue we added this optionality
• Display Tooltips ? : a number of tooltip are disabled when user want it  
• Results per page : the number of result found by page of search, largely used in seach pages (like for test plan , etc)
• Spoken languages : the list of spoken language ( useful in CAT)
• user's picture

User preference is more explained in this link : http://gazelle.ihe.net/node/141.

Connect as user

 Gazelle offer the possibility to the admin to view the GUI of the vendor, the same GUI configuration, and to  connect as the corresponding user; which could be useful when the vendor has a problem, and the admin want to see what it really looks like.

The administrator has the possibility to edit Administrations registred into gazelle, or to add new organization/companies.

To do so, the admin shall go to menu -> administration -> manage -> Manage Organizations.

 The page of this module looks like this:

For each organization, we can go to :

• its website
• the list of users related
• the list of contacts related
• the invoice of the institution

The table describes the information related to the institutions: the name, the keyword; the type, the number of related systems, the last modifier and the last modified time.The administrator has the possibility to view, edit or delete an institution.

Create New Organization

The administrator is able to create a new administration using the button "Add an organization".

The result of clicking on this button is the organization edit page:

View Mode

The view mode is possible using the loop :

The result of this page is a html description of all the information related to the institution:

• Organization Demographic Summary
• Mailing address
• The billing address

Edit Mode

the Edit mode is shown using the button

The result of this page is the same rendering for the vendor who create the organization, and which look like this:

The admin of gazelle TM can access to the list of contact of organizations, modify, delete or add new ones.

To access the administration of contacts, the admin shall go from the menu to administration -> Manage -> Manage Contacts

The main page looks like this:

 The button "Add a contact" allows to add a new contact.

The table describes the information related to contacts registred, and we can filter by organization.

The contacts displayed can be edited or deleted, as a vendor admin can do.

The management of systems contains 6 sub-sections listed below

A testing session in Gazelle Test Management is used to manage a testing event. It can be a connectathon, an accredited testing session, a projectathon or even a virtual testing session. Users registered in the application will be able to create new system for a testing session in particular or to import systems from other events.

The tool is able to manage several sessions at the same time; each session can have a different status.

Accessing the testing sessions

Management of sessions is performed from menu Administration --> Manage --> Manage sessions.

The first page you access to list the testing sessions registered in your instance of Gazelle Test Management. The highlited one (bold font) is the testing session you are currently logged into.

From this page, you can see what are the active testing sessions, active/inactive them, edit them or event delete them. You can also, by clicking on the green tick, set the one which will be used as default when a new user creates an account. Note that logged in user will also be able to acess the activated testing sessions; the other ones will be hidden from the list.

Creating a new testing session

From the Administration of testing sessions page, click on "Add an event"; a new form will be displayed. The following information are requested

• Year : when the testing event takes place
• Zone : where the testing event takes place
• Type : what type of event are you registering
• Description : will be used as title of the testing session
• Start date : beginning of the testing event itself
• End date : end of the testing event
• Registration deadline : after this date, users will not be able to alter their system (addition/removal of actor/profile)
• Mailing list URL and wiki URL are given for informational purpose only
• Logo URL : can be the link to an image in the tool (/img/gazelle.gif for instance) or an external link. It will be displayed in the right of the page when this testing session is selected by the user)
• Link associated to the logo : when clicking on the logo, user wil be redirected to that page
• Color: theme of Test Management can be customed and the background color can be different for each testing event. Note that the color of the text will not change, so be careful to use a color which will still allow the reading of the application
• Order in GUI : used to order the testing session in the pop-up used to change the current testing session of the logged in user

Then you can select several options : 

• If this event the default one for new users (Default testing session)
• Is Internet testing enabled (that means that users can enter their SUT endpoints outside of the testing event network)
• Is pre-connectathon testing requested (users will be expected to perform some in-house tests before showing up at the event)
• Is Gazelle Test Management used to manage the badges (Allow Participant registration)
• Hidden from list : if checked, users will not be able to select this testing session
• Critial Status : At some point during the event, you may want users to highlight the test instances they really need; enabling the critical status will allow users to mark some test instances as critical and will then be checked in priority by monitors
• Session closed: if the testing event is closed, users will not be able to create new test instances nor alter others
• Disable auto update result : the connectathon results are periodically computed, you can disable it for a testing session. Note that you might not want to disable it until a testing event is running since it will also prevent the tool from creating the test plan of the systems.

Then you can select a set of test types among the following ones :

• 17025 : used for accredited testing sessions, only tests of type 17025 Cofrac will be displayed to the user
• certification: only tests of type "certification" will be displayed to the user
• connectathon: only tests of type "connectathon" will be displayed to the user, this is the testing type to use in most cases
• HISTP was used in the USA in the context of a regional project
• interoperability-testbed enables the ITB (Interoperability Test bed) feature

The testing session administrators are used in the header of the test reports

Then, pick up the integration profiles for which the users will be allowed to register their systems.

Contact information

Here you need to give information about the person to contact for questions about the event.

Certificates menu URL

Depending of the events, the management of certifactes is not performed by the same tool. If you want users to share certificates using a specific tool, tick the "Display certificates menu" checkbox and enter the URL of the tool.

Financial section

Gazelle Test Management can generate the contract and the invoice, if this testing event requires a contract and you want the tool to manage it, tick the checkbox "Required a contract ?".

Note that the rule for computing fees currently applies in Gazelle Test Management is the following:

The amount is relative to the number of systems the company has registered, and marked "completed". You can state that the price for the first system is different from the one for the following. Regarding the fees for additional participants, it is the amount due per participant when the number of participants is strictly higher than 2 times the number of systems.

Currency code is used to express the currency to be used. Then you can custom the VAT and give the list of country VAT it the VAT of the country applies instead the global one (that's the case in Europe).

Finally, the contract and the invoice are generated based on a Jasper report, you need to provide the location of those *.jrxml files.

Testing management

From this point, you can randomly generate test instances for testing the tool. You can also delete all the test instances to reset the testing session.

Demonstrations liste

View demonstration

Edit demonstration

The system configuration administration is divided into 3 parts, reachable from the Administration --> Manage --> Configurations menu

• Manage Hosts' configuration : manage the host name and IP addresses assigned to systems for the event (in the event floor)
• All configurations : manage all the configuration of all the systems
• OIDs management : manage the OIDs to be used by system during the event

Network Configuration

Before managing the hosts and the system network configurations, you need to configure the network of the testing event. To do this, go to Configurations --> Network configuration Overview. This page is made of three sections materialized by three tabs.

Hosts configuration

This page shows to text area. In the first one, you can give tips to the user regarding the network configuration during the event. We usually provide the Wireless SSID and keys, the subnet information (netmask, gateway, DNS server, internal domain name and so on), the URL of the tools and their IP addresses.

In the second area, you are requested to provide the header of the host file so that people will be able to download a complete host file gathering the hostnames and addresses of all the systems connected during the connectathon.

Participants to the testing session who do not want to use DNS can download the host file and use it to configure their system. THIS OPTION IS NOT RECOMMENDED BUT WAS IMPLEMENTED FOR ONE DEVICE THAT COULD NOT USE DNS. DNS IS THE PREFERRED SOLUTION AS IT IS DYNAMIC !

• Configuration of host file on windows system
• Configuration of host file on MacOsX system
• Configuration of host file on Linux system

Configure IPs and DNS

Filling out those information will help the tool with assigning IP addresses and build the DNS and DNS reverse file. 

Example of DNS file header and DNS reverse file header are provided below.

; 
; BIND data file for local loopback interface
;
$TTL    604800
@    IN      SOA     ihe-europe.net. root.localhost. (
                              1         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                         604800 )       ; Negative Cache TTL
;
@                      IN      NS      ihe-europe.net.
@                   IN      A       127.0.0.1
$ORIGIN            ihe-europe.net.
;
;
;
ntp                  IN  A 192.168.0.10
dns                  IN  A 192.168.0.10
ihe-eu0            IN  A 192.168.0.10
gazelle            IN  A 192.168.0.10
proxy              IN  A 192.168.0.10
printer             IN  A 192.168.0.10
syslog           IN  A 192.168.0.13
central-archive     IN  A 192.168.0.11
central    IN  A 192.168.0.11
gazelle-tools     IN  A 192.168.0.13
dvtk    IN A 192.168.0.12

 $ORIGIN 168.192.in-addr.arpa.
$TTL    86400
@       IN      SOA     ihe-europe.net. root.ihe-europe.net. (
                              1         ; Serial
                         604800         ; Refresh
                          86400         ; Retry
                        2419200         ; Expire
                          86400 )       ; Negative Cache TTL
; authoritative name server
;       NS      127.0.0.1
@       IN      NS      dns.ihe-europe.net.
;
10.0  PTR     dns.ihe-europe.net.
10.0  PTR     ihe-eu0.ihe-europe.net.
10.0  PTR     proxy.ihe-europe.net.
11.0  PTR     central.ihe-europe.net.
11.0  PTR     central-archive.ihe-europe.net.
12.0  PTR     dvtk.ihe-europe.net.
12.0 PTR     connectathon2014.ihe-europe.net.
13.0 PTR     syslog.ihe-europe.net.
13.0 PTR     gazelle-tools.ihe-europe.net.

DNS automatic configuration on the server

In order to automatically update the DNS configuration on the server that is hosting the Gazelle Test Management application, one need to run the following script update_dns.csh

• Download the script and place it in the directory /opt/gazelle/dns
• install bind9 on the server :

apt-get install bind9 

You also need to configure bind9 (see documentation) in order to add a new zone that matches the requirement of the network on your session. 

In the file /etc/bind/named.conf.local add a line specific to your zone 

include "/etc/bind/named.conf.ihe-zones" 

Here is an example of the file named.conf.ihe-zones as used at one of our event for illustration. Note that the file makes references to the 2 files created by the update_dns.csh script.

zone "ihe.net" IN {
  type master;
  file "/etc/bind/zones.ihe.net";
  forwarders {
        213.33.99.70;
        };
};


zone "ihe-europe.net" IN {
  type master;
  file "/etc/bind/db.192.168";
  forwarders {
        213.33.99.70;
        };

};
zone "168.192.in-addr.arpa" {
  type master;
  file "/etc/bind/reverse.192.168";
};

Finally edit the script update_dns.csh and configure it in order to match the configuration of your network and the session in use.

Currently the DNS can only be updated for ONE SINGLE testing session. 

We recommend to use a cron to automatically update the DNS configuration on the server 

*/15 * * * * /opt/gazelle/dns/update_dns.csh

Then SUT can be configured to point to the DNS server that is configured that way. 

• Configuration of DNS client on windows system
• Configuration of DNS client on MacOsX system
• Configuration of DNS client on Linux system

Configure IPs and port for proxy

You may have configue the URL of the proxy in the application preferences. However, you might not want to use the Gazelle Proxy tool for all the testing event registered in the tool. From this page, you can enable/disable the use of the proxy during the event. In order to help users with using the Proxy, you are asked to provide the IP address used to contact it. 

When generating the system network configurations, if the proxy is enabled, each configuration will have a proxy port assigned. You need to provide the range of port used by the proxy so that the tool knows which values are allowed.

From this page, you can also start all the channels on the proxy; that means that the tool will gather all the system network configuration of receivers and tell the proxy to open the corresponding ports.

Manage Hosts' configuration

The list of hosts which is displayed on that page is restricted to the host assigned to the systems from the testing session you are currently logged in. If you need to access the list of hosts for another testing event, you need to change your testing session from the Gazelle --> Change testing session menu.

From the Manage Hosts' configuration page, you can assign internal IP addresses to all the hosts/systems registered for the testing event or you can even release all the IP addresses. The latter means that for each host defined in this testing session, the IP address will be set to null.

• A host name in Gazelle Test Management has the following attribute
• The system it is assigned to
• The host name
• An alias for this host name
• The assigned IPv4 address 
• A comment about its usage

You can edit each host and then get additional options/informations:

• Is the host external to the testing event network
• Assign the next available IP address from the range defined for the event

All Configurations

A network system configuration gives information to the user on how to configure their systems for the testing event and how to reach the systems of their partners for testing. Which type of configuration is requested by each actor is defined in Gazelle Master Model. 

From menu Administration --> Manage --> Configurations --> All configurations, you will access the list of configurations defined for the testing session you are currently logged in. From this page, you can edit each configuration one by one, approve it (it is usually an action to be performed by the SUT operator) or delete it.

"Add a config" button will allow you to create a new entry in the list for a system registered in the testing session you are currently logged in.

"Generate configs for selected session" will generate all the entries for all the systems registered in the testing session. Note that this task is long and performed in background; you will have to refresh the page latter on to get the list of configurations.

Note that if you select an Organization in the filter available at the top of the page, you will get a button to generate the configurations for all the systems owned by this organization; if you select a system from this same filter, you will get a button to generate the configuration for this specific system.

OIDs management

In some profiles, the messages or the documents described must be populated with OIDs. An Object Identifier shall be unique, it is composed of a root, managed by an authority and the rest manage by the system to which the root is assigned; in order to help vendor to configure their system, Gazelle Test Management offers a feature to manage the OID roots. 

From menu Administration --> Manage --> Configuration --> OIDs management, you will access a page divided into four tabs; they are described below:

OID - System assignement

In this tab, you will find the list of OID roots assigned to the systems registered within the tool. You can filter the list by testing session; knowing that the testing session set when you accessed the page is the testing session you are currently logged into.

Note that you can edit those values by clicking on the edit icon.

OID requirements

This section allows the administrator of the tool to define for which actors OIDs need to be defined and what this OID will be used for. You can edit, delete or create requirements. Before creating a new requirement, if you intent to use an OID different from the ones already used, first jump to OID Roots tab to define a new OID. Note that those OID requrements are common to all the testing sessions.

When you edit or create a requirement, you are ask to provide the list of Actor/Integraiton Profile/ Option tuples to which it applies; to do so, use the "add AIPO" button; select your AIPO and click on the "Add new AIPO" button.

You can also remove an AIPO from the list, only click on the red cross in the table on the corresponding line.

OID Roots

Here are listed all the OID roots which are used to build OIDs; the last value coming from the database is already displayed there. For each root, you can also provide a comment to inform the users what this root is used for.

You can edit and delete root OID, you can also create new ones; only click on the "Add a new OID Root" button and fill out the form which appears in the pop-up. Note that those roots are common to all the testing sessions.

OID Testing Session Management

From this section, you are allowed to perform three actions:

• Removing all the OIDs which have been assigned to the systems registered to the current testing session
• Removing and generating again all the OIDs for the current testing session
• Updating the OIDs assigned to the systems; that means that systems which have been newly added will get OIDs and if no requirements have been creating, they will be applied to the concerning systems.

The monitors are the persons who are present during the testing event to verify the tests performed by the SUT operators. The recruitment process is not descibed there neither the work of the monitor. This section focuses on how to set persons as monitor, how to say to which testing session they attend and how to create their list of tests, it means, what are the tests they will have to verify during the event.

First of all, all the users in Test Management who are aimed to be a monitor for a testing session shall have the "monitor_role" role. Refer to the User Administration part if you do not know how to grant users.

Then, under the Administration --> Manage --> Manage monitors, there are two entries. The first one "Manage monitors" will be used to link the users with role "monitor-role" to a testing session and then assign them a list of tests. The second entry "Assign monitors to tests" is useful if you want to assign a batch of monitors to a batch of tests.

Manage monitors

This page lists the monitors already link to the current testing session (the one you are currently logged into). For each monitor, beside his/her contact and connection information, you will get the number of tests which have been assigned to him/her. Note that above the table is given the number of monitors registered for the current event.

In the last column, buttons are available to view the detail of a monitor test list, print this test list, edit it or unassign the user from the list of monitors (the red cross).

When you edit the test assignments of a monitor, the list of already assigned tests is displayed, you can remove some of them by hitting the red cross. If you want to add some more, use the "Edit Test Assignment" button, il will open a new panel. You can filter the test either by domain, integration profile or actor. First select the criteria type, then select one domain or integration profile or actor and pick up the tests to assign to the current monitor.

At the bottom of the page, two buttons are available : the first one will open the "Assign monitors to tests" page and the second one opens a new panel in which you can pick up the users to add to the list of monitors. Monitors are sorted by organization. When you have made your choice, do not forget to hit the "Add monitors to activated session" button (bottom right corner); this button shall be hit before moving to another organization.

Assign monitors to tests

If you prefer to assign the monitors to a list of tests instead of assigning a list of test to a monitor, you can use this feature.

First, select a sub set of tests by applying filters. Then, click on the green tick in the Selection column. If you click on the icon located in the table header, it will select all the tests currently displayed in the table. To unselect a test / all the displayed tests, hit the grey tick.

When at least one test is selected, the number of monitors assigned to this selection is displayed below the table. Note that if several tests are selected, the number displayed represents the intersection of the monitors assigned to each test. If at least one monitor is assigned, the list is displayed below the table.

From this point, you can modify the list of monitors by clicking on the button "Modify list monitors", pick up the ones to add (or to remove) and it the "Save modifications" button.

It gives the administrator an overview of users attending to the connectathon. It helps planning the catering, tables...

A participant can register for some connectathon days, specify if he eats vegetarians and if he will attend the social event.

The administrator has an overview of who is going to attend the connectathon on moday, tuesday....

An administrator can add participants from the users list, contact list or create a new participant.

An administrator can remove a connectathon participant, or edit it.

An administrator can filter participants by organization

Edit testing session participants

Grading the systems during a testing event is a manual process performed by the testing session managers.This section of the administration manual does not focus on the rules to grade system (they might be different depending on the testing events) but it describes how to do it with Gazelle Test Management.

You will access the connectathon result page from menu Connectathon --> Connectathon --> Connectathon results.

This page is divided into two parts; first you can filter the results and below the results (restrained to the filter criteria) are displayed.

In the first panel, a button labeled "Update results" can be used to force the update of the results. It will not grade the system, it will retrieve some information from the database like the number of test instances performed by each system and compute an indicator to help you with grading the systems.

In the table, a line is displayed for each actor / integration profile / option (AIPO) tuple registered by a system; in Test Management, results are given at system level even if we usually communicate the results at company level.

• The column "Type" tells you if the system is supportive (S) or Thorough (T) for this AIPO.
• Column "R/O" indicates the number of required vs optional tests to be performed by the system for this AIPO
• Column "V" indicates the percentage of verified (successful) test instances versus the number of expected successful test instances
• Column "W" indicates how many test instances are waiting for verification
• Column "P" indicates how many test instances are in state "Partially verified" 
• Column "F" indicates how many test instances are failed
• In the "Partners" column, you will find, for each role involved in the test other than the one played by the system, the number of "used" partners versus the number of available ones. For each a tool tip give you the keyword of the role.
• In the Tests column, the magnifying glass opens a sub table which gathers all the test instances related to this AIPO. To close a sub-table, click again on the magnifying glass. To close all the sub tables you have previously displayed, use the "Close and reset all details" button available above the table.
• In the Results column, you can select the status for this line, it will be automatically saved

Finally, you can leave a comment to the user.

To help you focussing on the lines which need to be reviewed, lines are colorized and appears in grey if no result is set. 

This list of modules allows the admin to verify and to check the well functioning of the Test Management tool.

There are 4 types of KPIs:

• Tests kpi
• Systems kpi
• Monitor kpi
• Validator kpi

All KPIs can be exported in an excel file

This page allows you to monitor:

• memory usage through time
• active pages through time
• sessions through time 
• session details
• caches usage

In graphs trought time on the time axis you can move time cursors to zoom into a specific time.

Memory usage though time

Active pages through time 

Sessions through time

Session details

Caches usage