Updating Distribution S3P configuration.

- fixing the scripts and jmx files after stability long run failures.

Issue-ID: POLICY-3654
Change-Id: I0ff0bf625f226f1b71664c1817cef65fbd5cf5a6
Signed-off-by: adheli.tavares <adheli.tavares@est.tech>

1 files changed, 3 insertions, 10 deletions

diff --git a/testsuites/stability/src/main/resources/testplans/README.stability.md b/testsuites/stability/src/main/resources/testplans/README.stability.md
index b73d7927..e581acaf 100644
--- a/testsuites/stability/src/main/resources/testplans/README.stability.md
+++ b/testsuites/stability/src/main/resources/testplans/README.stability.md
@@ -6,18 +6,11 @@ Download JMeter 5.0 from https://jmeter.apache.org/download_jmeter.cgi, and extr
 2. Run the setup-components script found within simulator setup.
 This will launch MariaDB, PDPSimulator, PAP, Policy-API and DMaap Simulator as docker containers.
 
-3. Launch the policy distribution service by running the setup-distribution script found within distributionsetup.
-If you are running all of the components locally you will need to edit the port that distribution starts on as it is
-currently 6969 which conflicts with the policy API port.
-This will launch policy-distribution as a docker container and takes 2 arguments, PAP IP and API IP.
-If you are running locally these will be 127.0.0.1. If on a VM enter the VM IP.
-```
-setup-distribution.sh 127.0.0.1 127.0.0.1
-```
+3. Launch the policy distribution service by running the start script found within setup folder.
 
-4. Run the JMeter stability test
+4. Run the JMeter stability test from testplans folder
 ```
-rm -f stability.log; <jmeter_dir>/bin/jmeter.sh -t stability.jmx -n -Jhost=<pdp service hostname> -Jduration=100 -l stability.log
+./run_test.sh
 ```
 Search for 'get policy failed' in the stability.log file to see if there is any errors found during the stability test.