diff options
| author |   lapentafd <francesco.lapenta@est.tech> | 2022-04-12 11:23:22 +0100 |
|---|---|---|
| committer | lapentafd <francesco.lapenta@est.tech> | 2022-04-12 12:17:54 +0100 |
| commit | 45ce655d0a7a1568e3518bc968f968a41688f99d (patch) | |
| tree | cb952120e4bbef766e296969834f77963f389333 /docs/development/devtools/clamp-cl-participant-protocol-smoke.rst | |
| parent | 4236d55e6df1c17318995a65ad0a6e9411462456 (diff) | |
Fix typos in policy docs devtools
Update images names, that were not displaying
Issue-ID: POLICY-3941
Signed-off-by: lapentafd <francesco.lapenta@est.tech>
Change-Id: I85115478f285028ad02644614bee9c0f7f178206
Diffstat (limited to 'docs/development/devtools/clamp-cl-participant-protocol-smoke.rst')
| -rw-r--r-- | docs/development/devtools/clamp-cl-participant-protocol-smoke.rst | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/development/devtools/clamp-cl-participant-protocol-smoke.rst b/docs/development/devtools/clamp-cl-participant-protocol-smoke.rst index 4ad03984..09ab453f 100644 --- a/docs/development/devtools/clamp-cl-participant-protocol-smoke.rst +++ b/docs/development/devtools/clamp-cl-participant-protocol-smoke.rst @@ -9,7 +9,7 @@ CLAMP Participant Protocol Smoke Tests The CLAMP Automation Composition Participant protocol is an asynchronous protocol that is used by the CLAMP runtime to coordinate life cycle management of Automation Composition instances. -This document will serve as a guide to do smoke tests on the different usecases that are involved when +This document will serve as a guide to do smoke tests on the different use cases that are involved when working with the Participant protocol and outline how they operate. It will also show a developer how to set up their environment for carrying out smoke tests on the participants. @@ -17,7 +17,7 @@ It will also show a developer how to set up their environment for carrying out s ************** This section will show the developer how to set up their environment to start testing participants with some -instructions on how to carry out the tests. There are a number of prerequisites. Note that this guide is written by a +instructions on how to carry out the tests. There are several prerequisites. Note that this guide is written by a Linux user - although the majority of the steps show will be exactly the same in Windows or other systems. 2.1 Prerequisites @@ -39,7 +39,7 @@ Linux user - although the majority of the steps show will be exactly the same in - policy-api for communication between policy participant and policy-framework In this setup guide, we will be setting up all the components technically required for a working convenient -dev environment. We will not be setting up all of the participants - we will setup only the policy participant as an +dev environment. We will not be setting up all the participants - we will setup only the policy participant as an example. 2.2.1 MariaDB Setup @@ -81,7 +81,7 @@ Test result: 3.3 Participant Priming ======================= -When a automation composition is primed, the portion of the Automation Composition Type Definition and Common Property values for the participants +When an automation composition is primed, the portion of the Automation Composition Type Definition and Common Property values for the participants of each participant type mentioned in the Automation Composition Definition are sent to the participants. Action: Invoke a REST API to prime acm type definitions and set values of common properties @@ -94,7 +94,7 @@ Test result: 3.4 Participant DePriming ========================= -When a automation composition is de-primed, the portion of the Automation Composition Type Definition and Common Property values for the participants +When an automation composition is de-primed, the portion of the Automation Composition Type Definition and Common Property values for the participants of each participant type mentioned in the Automation Composition Definition are deleted on participants. Action: Invoke a REST API to deprime acm type definitions |