RIC:1060: Change in PTL

[ric-plt/sdl.git] / README.md

diff --git a/README.md b/README.md
index 4c76fd9..a8f9a35 100644 (file)
--- a/README.md
+++ b/README.md
@@ -188,7 +188,7 @@ line options gtest supports, for example:
 Enable unit test gcov code coverage analysis by configuring gcov reporting
 directory:
 
-    configure --with-gcov-report-dir=DIR
+    ./configure --with-gcov-report-dir=DIR
 
 Directory can be an absolute path or a relative path to an SDL source root.
 Unit test build creates directory if it does not exist.
@@ -203,11 +203,23 @@ a directory, what was defined by '--with-gcov-report-dir' configure option.
 In addition, graphical gcov front-ends such as lcov can be used for coverage
 analysis:
 
-       lcov --directory tst/ --directory src --capture --output-file coverage.info
-       genhtml coverage.info --output-directory out
+    lcov --directory tst/ --directory src --capture --output-file coverage.info
+    genhtml coverage.info --output-directory out
 
 Open the out/index.html using any web browser.
 
+## Docker Tests
+
+It's also possible to test SDL compilation, run unit tests and test building of
+rpm and Debian packages in a Docker:
+
+    docker build  --no-cache -f docker_test/Dockerfile-Test -t sdltest:latest .
+
+If needed, ready rpm and Debian packages can be copied from Docker to host. In
+below example packages are copied to host's /tmp/sdltest-packages directory:
+
+    docker run -v /tmp/sdltest-packages:/export sdltest:latest /export
+
 ## Using SDL in application pod
 
 SDL is not yet available in O-RAN-SC PackageCloud.io repository.