From 8fadfb9667186910af1b9b6c31b9bb673057f729 Mon Sep 17 00:00:00 2001 From: FrancescoFioraEst Date: Wed, 17 Apr 2024 11:42:58 +0100 Subject: Add migration in integration tests Issue-ID: POLICY-4972 Change-Id: I40c554fcb062b4928663bbfd5a03ddd2dd1f6805 Signed-off-by: FrancescoFioraEst --- README.md | 3 +++ 1 file changed, 3 insertions(+) (limited to 'README.md') diff --git a/README.md b/README.md index 709eee3d..c1e90e5f 100644 --- a/README.md +++ b/README.md @@ -26,6 +26,9 @@ Steps involved in running CSIT in kubernetes: 4. Invokes the respective robot test file for the project supplied by the user. The test execution results can be viewed from the logs of policy-csit-robot pod. +Running Policy CSIT in docker: +To run CSIT in docker, docker/csit/run-project-csit.sh script can be invoked with the argument {project_name}. + Running Policy Regression Tests: ACM regression tests can be invoked using the script docker/csit/run-acm-regression.sh with the arguments {ACM-R release name} {participant release name} For example, if ACM-R and participants needs to be tested for backward compatbility between montreal and london versions, the script can be invoked -- cgit 1.2.3-korg