ml-testing-toolkit 18.13.0

package/documents/User-Guide-OAuth-Server-Deployment.md

@@ -0,0 +1,283 @@
+# Users Guide
+
+## _OAuth Server Installation & Configuration (Hosted mode only)_
+
+### Introduction
+
+This document provides a basic user guide to **install and configure an oAuth server and configure for the testing toolkit**. .
+
+To use **Hosting Capability** in the testing toolkit a Scheme / Hub should provide their OAuth server details in the toolkit for providing user authentication in the toolkit web UI and connection manager UI. Typically Schemes / Hubs may already have their own OAuth servers. This guide is just in case they want to implement it from scratch and in any case, to have a reference about the flow.
+
+We are using an open source oAuth server called **Keycloak**. Keycloak is "Open Source Identity and Access Management" software and the documentation can be found at https://www.keycloak.org/
+
+
+**Table of Contents**
+
+1. [Deploy Keycloak Server](#1-deploy-keycloak-server)
+
+2. [Configure the KeyCloak Server](#2-configure-the-keycloak-server)
+
+    2.1 [Login to the admin console](#21-login-to-the-admin-console)
+
+    2.2 [Create a Realm](#22-create-a-realm)
+
+    2.3 [Create a Client](#23-create-a-client)
+
+    2.4 [Change some Client settings](#24-change-some-client-settings)
+  
+    2.5 [Create Groups](#25-create-groups)
+  
+    2.6 [Create Hub User](#26-create-hub-user)
+  
+    2.7 [Create DFSP User](#27-create-dfsp-user)
+
+3. [Obtain the required details from KeyCloak Server](#3-obtain-the-required-details-from-keycloak-server)
+
+    3.1 [Get the Client ID and Secret](#31-get-the-client-id-and-secret)
+  
+    3.2 [Get the Public Key for decoding the Access Token](#32-get-the-public-key-for-decoding-the-access-token)
+
+4. [Configure the Testing Toolkit](#4-configure-the-testing-toolkit)
+
+    4.1 [Enable oAuth authentication](#41-enable-oauth-authentication)
+
+5. [Configure the Connection Manager](#5-configure-the-connection-manager)
+
+    5.1 [Enable oAuth authentication in Connection Manager](#51-enable-oauth-authentication-in-connection-manager)
+
+
+### 1. Deploy Keycloak Server
+
+There are many ways to deploy Keycloak. Here we are using docker method to run this service easily.
+
+Just execute the following command to run the service
+
+```
+docker run -p 8080:8080 -e KEYCLOAK_USER=admin -e KEYCLOAK_PASSWORD=admin quay.io/keycloak/keycloak:10.0.2
+```
+
+For additional documentation please refer https://www.keycloak.org/getting-started/getting-started-docker
+
+### 2. Configure the KeyCloak Server
+
+#### 2.1 Login to the admin console
+
+Open the URL http://localhost:8080/auth/admin and login with username 'admin' and password 'admin' (You can change these values in the command we used for start the server)
+
+#### 2.2 Create a Realm
+
+* Hover the mouse over the dropdown in the top-left corner where it says Master, then click on Add realm
+
+* Fill in the form with the following values:
+
+  ```
+  Name: testingtoolkit
+  ```
+* Click Create
+
+#### 2.3 Create a Client
+
+* Click Clients (left-hand menu)
+
+* Click Create (top-right corner of table)
+
+* Fill in the form with the following values:
+  ```
+  Client ID : ttk
+  Client Protocol : openid-connect
+  ```
+
+#### 2.4 Change some Client settings
+
+* Click Clients (left-hand menu)
+
+* Click on the new client (ttk)
+
+* Change the following values in Settings tab:
+  ```
+  Access Type : confidential
+  Service Accounts Enabled : ON
+  Authorization Enabled: ON
+  Valid Redirect URIs: Any random URI for now
+  Fine Grain OpenID Connect Configuration -> Access Token Signature Algorithm: RS256
+  Fine Grain OpenID Connect Configuration -> ID Token Signature Algorithm: RS256
+  ```
+
+* Create the following entries in the Mappers tab:
+
+  | Name | Mapper Type | Properties | Add to ID token | Add to Access token |
+  | --- | --- | --- | --- | --- |
+  | dfspId | User Attribute | User Attribute: __dfspId__ <br /> Token Claim Name: __dfspId__ <br /> Claim JSON Type: __String__ | ON | ON |
+  | aud | Audience | Included Client Audience : __ttk__ <br /> Included Custom Audience: __aud__ |
+  | Groups | Group Membership | Token Claim Name: __groups__ <br /> Full group path: __OFF__ | ON | ON |
+
+#### 2.5 Create Groups
+
+* Click Groups (left-hand menu)
+
+* Click New (top-right corner of table)
+
+* Create the following groups:
+
+  ```
+  Application/DFSP:dfsp1
+  Application/MTA
+  Application/PTSA
+  Internal/everyone
+  ```
+
+#### 2.6 Create Hub User
+
+* Click Users (left-hand menu)
+
+* Click Add user (top-right corner of table)
+
+* Fill in the form with the following values:
+  ```
+  Username: hub
+  First Name: Hub
+  Last Name: User
+  User Enabled: ON
+  Email Verified: OFF
+  ```
+
+* Click on the tab "Attributes" and add the following
+  ```
+  Key: dfspId
+  Value: hub
+  ```
+
+* Click on the tab "Credentials" and create the password
+  ```
+  Password: <Some password for the Hub>
+  Password Confirmation: <Some password for the Hub>
+  Temporary: OFF
+  ```
+
+* Click on the tab "Groups" and join the following groups
+  ```
+  Application/PTA
+  Internal/everyone
+  ```
+
+#### 2.7 Create DFSP User
+
+* Click Users (left-hand menu)
+
+* Click Add user (top-right corner of table)
+
+* Fill in the form with the following values:
+  ```
+  Username: user1
+  First Name: User
+  Last Name: One
+  User Enabled: ON
+  Email Verified: OFF
+  ```
+
+* Click on the tab "Attributes" and add the following
+  ```
+  Key: dfspId
+  Value: dfsp1
+  ```
+
+* Click on the tab "Credentials" and create the password
+  ```
+  Password: <Some password for User1>
+  Password Confirmation: <Some password for User1>
+  Temporary: OFF
+  ```
+
+* Click on the tab "Groups" and join the following groups
+  ```
+  Application/DFSP:dfsp1
+  Application/MTA
+  Internal/everyone
+  ```
+
+### 3. Obtain the required details from KeyCloak Server
+
+#### 3.1 Get the Client ID and Secret
+
+* Click Clients (left-hand menu)
+
+* Click on the client 'ttk' in the table
+
+* Note down the __Client ID__
+
+* Click on the tab 'Credentials' and note down the __Secret__
+
+#### 3.2 Get the Public Key for decoding the Access Token
+
+* Click Realm Settings (left-hand menu)
+
+* Click on the tab 'Keys'
+
+* Click on the '__Public Key__' of RS256 Algorithm and note down the key
+
+
+### 4. Configure the Testing Toolkit
+
+#### 4.1 Enable oAuth authentication
+
+* Change the system_config.json file with the following values
+  ```
+  "HOSTING_ENABLED": true,
+  "OAUTH": {
+    "AUTH_ENABLED": true,
+    "APP_OAUTH_CLIENT_KEY": "ttk",
+    "APP_OAUTH_CLIENT_SECRET": "<CLIENT_SECRET>",
+    "MTA_ROLE": "Application/MTA",
+    "PTA_ROLE": "Application/PTA",
+    "EVERYONE_ROLE": "Internal/everyone",
+    "OAUTH2_TOKEN_ISS": "http://<KEYCLOAK_HOST>:8080/auth/realms/testingtoolkit",
+    "OAUTH2_ISSUER": "http://<KEYCLOAK_HOST>:8080/auth/realms/testingtoolkit/protocol/openid-connect/token",
+    "EMBEDDED_CERTIFICATE": "-----BEGIN PUBLIC KEY-----\n<PUBLIC_KEY_COPIED_FROM_KEYCLOAK>\n-----END PUBLIC KEY-----"
+  }
+  ```
+
+* Change the following values of the service mojaloop-testing-toolkit-ui in _'docker-compose.yml'_
+  ```
+    environment:
+      - API_BASE_URL=http://localhost:5050
+      - AUTH_ENABLED=TRUE
+  ```
+
+### 5. Configure the Connection Manager
+
+#### 5.1 Enable oAuth authentication in Connection Manager
+
+* Change the environment variables of the service 'connection-manager-api' in the _'connection-manager/docker-compose.yml'_
+  ```
+  environment:
+    DATABASE_HOST: connection-manager-db
+    DATABASE_PORT: 3306
+    DATABASE_USER: mcm
+    DATABASE_PASSWORD: mcm
+    DATABASE_SCHEMA: mcm
+    MYSQL_ROOT_PASSWORD: <MYSQL_PASSWORD>
+    PORT: 5061
+    P12_PASS_PHRASE: 'SOME_S3C4R3_P@SS'
+    OAUTH2_ISSUER: http://<KEYCLOAK_HOST>:8080/auth/realms/testingtoolkit/protocol/openid-connect/token
+    OAUTH2_TOKEN_ISS: http://<KEYCLOAK_HOST>:8080/auth/realms/testingtoolkit
+    AUTH_ENABLED: 'TRUE'
+    APP_OAUTH_CLIENT_KEY: ttk
+    MTA_ROLE: 'Application/MTA'
+    PTA_ROLE: 'Application/PTA'
+    EVERYONE_ROLE: 'Internal/everyone'
+    APP_OAUTH_CLIENT_SECRET: <CLIENT_SECRET>
+    EMBEDDED_CERTIFICATE: |-
+      -----BEGIN PUBLIC KEY-----
+      <PUBLIC_KEY_COPIED_FROM_KEYCLOAK>
+      -----END PUBLIC KEY-----
+  ```
+
+* Change the environment variables of the service 'connection-manager-ui' in the _'connection-manager/docker-compose.yml'_
+  ```
+    environment:
+      - API_BASE_URL=http://localhost:5050
+      - AUTH_ENABLED=TRUE
+  ```
+
+
+Now you can login with the username user1 in both testing toolkit UI and connection manager UI

package/documents/User-Guide-Onboarding-DFSP.md

@@ -0,0 +1,197 @@
+# Mojaloop Testing Toolkit
+
+## _Onboarding DFSP_
+
+**Table of Contents**
+
+1. [Running the toolkit](#1-running-the-toolkit)
+
+2. [Settings](#2-settings)
+
+3. [Run collections](#3-run-collections)
+
+    3.1 [Web UI](#31-web-ui)
+
+      3.1.1 [Import Collection](#311-import-collection)
+
+      3.1.2 [Import Environment](#312-import-environment)
+
+      3.1.3 [Execute Collection](#313-execute-collection)
+
+      3.1.4 [View Report](#314-view-report)
+
+    3.2 [CLI tool](#32-cli-tool)
+
+      3.2.1 [Help Screen](#321-help-screen)
+
+      3.2.2 [Execute Collection](#322-execute-collection)
+
+      3.2.3 [View Report](#323-view-report)
+
+## 1. Running the toolkit
+
+The following softwares should be installed on your system to run the toolkit.
+
+* Git
+* Docker
+
+Please execute the following lines to build and run the tool. 
+
+```bash
+git clone https://github.com/mojaloop/ml-testing-toolkit
+cd ml-testing-toolkit
+docker-compose up
+```
+
+To update the **Mojaloop Testing Toolkit** to the latest version and rebuild, please run the following
+
+```bash
+cd ml-testing-toolkit
+git pull
+docker-compose build
+docker-compose up
+```
+
+You should get the web interface on http://localhost:6060
+
+If you want to test the tool for the whole functionality like schema validation, additional validation and callback generation ..etc, you can initiate a transfer cycle from mojaloop simulator UI.
+
+Please follow the below steps from the ml-testing-toolkit folder
+
+```bash
+cd simulator
+docker-compose up
+```
+
+The above command will start the services scheme-adapter, mojaloop-simulator and mojaloop-simulator-ui.
+
+## 2 Settings
+
+You will need to create a new user for **MSISDN** = **9876543210**. In the **Mojaloop Simulator UI**, select _**+ Add User**_ button on the _**Config Inbound**_ navigation tab. Below screenshot is a sample based on the sample data used within this document. Click on the _**√ Submit**_ button when done. 
+
+![Create Inbound User on Simulator](/assets/images/create-inbound-user-simulator.png)
+
+The _**SETTINGS**_ navigation tab will open to the **SETTINGS** window. Below is the default view of this page.
+
+![Opening Default Settings](/assets/images/opening-default-settings.png)
+
+- The **SETTINGS** window consist of the following two windows;
+  - On the left **Runtime Global Configuration** displays the actual configuration that is effectively active by the **Mojaloop Testing Toolkit** service.
+  - On the right **Edit Global Configuration** amongst a couple of other options, it allows you to edit the values manually. Should you elect to use other environment values you can disable the default values by selecting the _**Override with Environment Variable**_ option.
+
+- In a default docker deployment, the environment values will be provided in the _local.env_ file in the project root directory.
+
+![Override with Environment Variable](/assets/images/override-with-environment-variable.png)
+
+## 3 Run Collections
+
+### 3.1 Web UI
+
+This sections will enable you to intiate requests from the testing toolkit to your DFSP implementation.
+
+The user can create a collection of operations and add a number of assertions to these operations. The assertions can be setup and customized to support your testing requirements and verify both positive and negative requests and responses. 
+
+Selecting the _**Outbound Request**_ navigation tab on the left side, the following will open in the main display window. 
+
+![Outbound display opening](/assets/images/outbound-display-opening.png)
+
+#### 3.1.1 Import Collection
+
+By selecting the _**Import Collection**_ button, it will allow you to import a collection or multiple collections. For your exploration, sample collections are available under the project root directory under [/examples/collections](/examples/collections) sub directory. To select one of the sample files, on the file explorer window that poped up when you selected the _**Import Collection**_ button, navigate to [/examples/collections/dfsp](/examples/collections/dfsp) under the project root directory. Select the ```p2p_happy_path.json``` file to import into the **Mojaloop Testing Toolkit** application. This sample file consist of a couple of test samples. You could add more test cases by clicking on _Add Test Case_ button
+
+#### 3.1.2 Import Environment
+
+By selecting the _**Import Environment**_ button, it will allow you to import input values. For your exploration, sample environments are available under the project root directory under [/examples/environments](/examples/environments) sub directory. To select one of the sample files, on the file explorer window that poped up when you selected the _**Import Environment**_ button, navigate to [/examples/environments](/examples/environments) under the project root directory. Select the ```dfsp_local_environment.json``` file to import into the **Mojaloop Testing Toolkit** application. This sample file consist of a couple of input values.
+
+It is possible to update the **Input Values** on the right hand side window. Additional input values can be added, by selecting the _**Add Input Value**_ button on the top right of this right hand side window. These values relates to the specified variable that you can select and use in any **Request** that you create. The process is straight forward. Provide a name for the new input value and click on the _**Add**_ button. To update values of exisiting variable(s) to the **Input Values**, simply select the value next to the variable and type in a new value. It will then be available for use in the test cases imported earlier.
+
+#### 3.1.3 Execute Collection
+
+You could execute the whole template by clicking on _Send_ button in the top right corner.
+
+#### 3.1.4 View Report
+
+You could download a report in several formats by clicking on _Download Report_ in the top right corner:
+- JSON
+- HTML
+- Printer Friendly HTML
+
+### 3.2 CLI tool
+
+#### 3.2.1 Help screen
+
+The help screen allows you to see the usage, possible options and default values
+
+command: 
+
+```
+node src/cli_client/client -h
+```
+
+output:
+
+```
+Usage: client [options]
+
+Options:
+  -v, --version                             output the version number
+  -c, --config <config>                     default configuration: {"mode": "outbound", "reportFormat": "json"}
+  -m, --mode <mode>                         default: "outbound" --- supported modes: "monitoring", "outbound"
+  -i, --input-files <inputFiles>            csv list of json files or directories; required when the mode is "outbound" --- supported formats: "json"
+  -e, --environment-file <environmentFile>  required when the mode is "outbound" --- supported formats: "json"
+  --report-format <reportFormat>            default: "json" --- supported formats: "json", "html", "printhtml"
+  --report-filename <reportFilename>        default: generated by the backend
+  -h, --help                                output usage information
+```
+
+#### 3.2.2 Execute Collection
+
+command:
+
+```
+node src/cli_client/client -m outbound -i examples/collections/dfsp/p2p_happy_path.json -e examples/environments/dfsp_local_environment.json --report-format html
+```
+
+output:
+
+```
+Listening on outboundProgress events...
+ ████████████████████████████████████████ 100% | ETA: 0s | 3/3
+--------------------TEST CASES--------------------
+P2P Transfer Happy Path
+        Get party information - GET - /parties/{Type}/{ID} - [8/8]
+        Send quote - POST - /quotes - [11/11]
+        Send transfer - POST - /transfers - [9/9]
+--------------------TEST CASES--------------------
+┌───────────────────────────────────────────────────────┐
+│                        SUMMARY                        │
+├───────────────────────┬───────────────────────────────┤
+│ Total assertions      │ 28                            │
+├───────────────────────┼───────────────────────────────┤
+│ Passed assertions     │ 28                            │
+├───────────────────────┼───────────────────────────────┤
+│ Failed assertions     │ 0                             │
+├───────────────────────┼───────────────────────────────┤
+│ Total requests        │ 3                             │
+├───────────────────────┼───────────────────────────────┤
+│ Total test cases      │ 1                             │
+├───────────────────────┼───────────────────────────────┤
+│ Passed percentage     │ 100.00%                       │
+├───────────────────────┼───────────────────────────────┤
+│ Started time          │ Mon, 01 Jun 2020 14:46:20 GMT │
+├───────────────────────┼───────────────────────────────┤
+│ Completed time        │ Mon, 01 Jun 2020 14:46:21 GMT │
+├───────────────────────┼───────────────────────────────┤
+│ Runtime duration      │ 832 ms                        │
+├───────────────────────┼───────────────────────────────┤
+│ Average response time │ NA                            │
+└───────────────────────┴───────────────────────────────┘
+TTK-Assertion-Report-dfsp-p2p-tests-2020-06-01T14:46:21.303Z.html was generated
+Terminate with exit code 0
+```
+
+#### 3.2.3 View Report
+
+You will find the report in the project folder.
+
+- default name format: 'TTK-Assertion-Report-{collection-name}-{ISO-date}.{report-format}'

package/documents/User-Guide-Onboarding-HUB.md

@@ -0,0 +1,191 @@
+
+# Mojaloop Testing Toolkit
+
+## _Onboarding HUB_
+
+**Table of Contents**
+
+1. [Running the toolkit](#1-running-the-toolkit)
+
+2. [Settings](#2-settings)
+
+3. [Run collections](#3-run-collections)
+
+    3.1 [Web UI](#31-web-ui)
+
+      3.1.1 [Import Collection](#311-import-collection)
+
+      3.1.2 [Import Environment](#312-import-environment)
+
+      3.1.3 [Execute Collection](#313-execute-collection)
+
+      3.1.4 [View Report](#314-view-report)
+
+    3.2 [CLI tool](#32-cli-tool)
+
+      3.2.1 [Help Screen](#321-help-screen)
+
+      3.2.2 [Execute Collection](#322-execute-collection)
+
+      3.2.3 [View Report](#323-view-report)
+
+## 1. Running the toolkit
+
+The following softwares should be installed on your system to run the toolkit.
+
+* Git
+* Docker
+
+Please execute the following lines to build and run the tool. 
+
+```bash
+git clone https://github.com/mojaloop/ml-testing-toolkit
+cd ml-testing-toolkit
+docker-compose up
+```
+
+To update the **Mojaloop Testing Toolkit** to the latest version and rebuild, please run the following
+
+```bash
+cd ml-testing-toolkit
+git pull
+docker-compose build
+docker-compose up
+```
+
+You should get the web interface on http://localhost:6060
+
+## 2 Settings
+
+Setup database
+
+After executing hub setup collection (Refer mojaloop documentation for more information), click on **Load Sample** button
+in Outbound Requests section and import examples/collections/provisioning/testingtoolkitdfsp.json collection from provisioning tab
+and examples/environments/hub_local_environment.json environment from hub tab
+
+The _**SETTINGS**_ navigation tab will open to the **SETTINGS** window. Below is the default view of this page.
+
+![Opening Default Settings](/assets/images/opening-default-settings.png)
+
+- The **SETTINGS** window consist of the following two sections;
+  - On the left **Runtime Global Configuration** displays the actual configuration that is effectively active by the **Mojaloop Testing Toolkit** service.
+  - On the right **Edit Global Configuration** amongst a couple of other options, it allows you to edit the values manually. Should you elect to use other environment values you can disable the default values by selecting the _**Override with Environment Variable**_ option.
+
+- In a default docker deployment, the environment values will be provided in the _local.env_ file in the project root directory.
+
+![Override with Environment Variable](/assets/images/override-with-environment-variable.png)
+
+## 3 Run Collections
+
+### 3.1 Web UI
+
+This sections will enable you to intiate requests from the testing toolkit to your DFSP implementation.
+
+The user can create a collection of operations and add a number of assertions to these operations. The assertions can be setup and customized to support your testing requirements and verify both positive and negative requests and responses. 
+
+Selecting the _**Outbound Request**_ navigation tab on the left side, the following will open in the main display window. 
+
+![Outbound display opening](/assets/images/outbound-display-opening-hub.png)
+
+#### 3.1.1 Import Collection
+
+By selecting the _**Import Collection**_ button, it will allow you to import a collection or multiple collections. For your exploration, sample collections are available under the project root directory under [/examples/collections](/examples/collections) sub directory. To select one of the sample files, on the file explorer window that poped up when you selected the _**Import Collection**_ button, navigate to [/examples/collections/dfsp](/examples/collections/dfsp) under the project root directory. Select the ```p2p_happy_path.json``` file to import into the **Mojaloop Testing Toolkit** application. This sample file consist of a couple of test samples. You could add more test cases by clicking on _Add Test Case_ button
+
+#### 3.1.2 Import Environment
+
+By selecting the _**Import Environment**_ button, it will allow you to import input values. For your exploration, sample environments are available under the project root directory under [/examples/environments](/examples/environments) sub directory. To select one of the sample files, on the file explorer window that poped up when you selected the _**Import Environment**_ button, navigate to [/examples/environments](/examples/environments) under the project root directory. Select the ```dfsp_local_environment.json``` file to import into the **Mojaloop Testing Toolkit** application. This sample file consist of a couple of input values.
+
+It is possible to update the **Input Values** on the right hand side window. Additional input values can be added, by selecting the _**Add Input Value**_ button on the top right of this right hand side window. These values relates to the specified variable that you can select and use in any **Request** that you create. The process is straight forward. Provide a name for the new input value and click on the _**Add**_ button. To update values of exisiting variable(s) to the **Input Values**, simply select the value next to the variable and type in a new value. It will then be available for use in the test cases imported earlier.
+
+#### 3.1.3 Execute Collection
+
+_IMPORTANT_: please make sure that the environment is updated based on your setup or update input values before execution
+
+You could execute the whole template by clicking on _Send_ button in the top right corner.
+
+#### 3.1.4 View Report
+
+You could download a report in several formats by clicking on _Download Report_ in the top right corner:
+- JSON
+- HTML
+- Printer Friendly HTML
+
+### 3.2 CLI tool
+
+#### 3.2.1 Help screen
+
+The help screen allows you to see the usage, possible options and default values
+
+command: 
+
+```
+node src/cli_client/client -h
+```
+
+output:
+
+```
+Usage: client [options]
+
+Options:
+  -v, --version                             output the version number
+  -c, --config <config>                     default configuration: {"mode": "outbound", "reportFormat": "json"}
+  -m, --mode <mode>                         default: "outbound" --- supported modes: "monitoring", "outbound"
+  -i, --input-files <inputFiles>            csv list of json files or directories; required when the mode is "outbound" --- supported formats: "json"
+  -e, --environment-file <environmentFile>  required when the mode is "outbound" --- supported formats: "json"
+  --report-format <reportFormat>            default: "json" --- supported formats: "json", "html", "printhtml"
+  --report-filename <reportFilename>        default: generated by the backend
+  -h, --help                                output usage information
+```
+
+#### 3.2.2 Execute Collection
+
+command:
+
+```
+node src/cli_client/client -m outbound -i examples/collections/dfsp/p2p_happy_path.json -e examples/environments/dfsp_local_environment.json --report-format html
+```
+
+output:
+
+```
+Listening on outboundProgress events...
+ ████████████████████████████████████████ 100% | ETA: 0s | 3/3
+--------------------TEST CASES--------------------
+P2P Transfer Happy Path
+        Get party information - GET - /parties/{Type}/{ID} - [8/8]
+        Send quote - POST - /quotes - [11/11]
+        Send transfer - POST - /transfers - [9/9]
+--------------------TEST CASES--------------------
+┌───────────────────────────────────────────────────────┐
+│                        SUMMARY                        │
+├───────────────────────┬───────────────────────────────┤
+│ Total assertions      │ 28                            │
+├───────────────────────┼───────────────────────────────┤
+│ Passed assertions     │ 28                            │
+├───────────────────────┼───────────────────────────────┤
+│ Failed assertions     │ 0                             │
+├───────────────────────┼───────────────────────────────┤
+│ Total requests        │ 3                             │
+├───────────────────────┼───────────────────────────────┤
+│ Total test cases      │ 1                             │
+├───────────────────────┼───────────────────────────────┤
+│ Passed percentage     │ 100.00%                       │
+├───────────────────────┼───────────────────────────────┤
+│ Started time          │ Mon, 01 Jun 2020 14:46:20 GMT │
+├───────────────────────┼───────────────────────────────┤
+│ Completed time        │ Mon, 01 Jun 2020 14:46:21 GMT │
+├───────────────────────┼───────────────────────────────┤
+│ Runtime duration      │ 832 ms                        │
+├───────────────────────┼───────────────────────────────┤
+│ Average response time │ NA                            │
+└───────────────────────┴───────────────────────────────┘
+TTK-Assertion-Report-dfsp-p2p-tests-2020-06-01T14:46:21.303Z.html was generated
+Terminate with exit code 0
+```
+
+#### 3.2.3 View Report
+
+You will find the report in the project folder.
+
+- default name format: 'TTK-Assertion-Report-{collection-name}-{ISO-date}.{report-format}'