Actualize stress tests README (openvinotoolkit#5698)

tests/stress_tests/README.md

@@ -34,44 +34,47 @@ one at a time to mitigate memory statistics pollution. You can use
 
 Stress tests should be built in 2 steps.
 
-1. Build `dldt`
+1. Build `openvino`
 
-Build `dldt` as usual but with `-DENABLE_TESTS=ON`.
+Build `openvino` as usual but with `-DENABLE_TESTS=ON`.
 
 2. Build `stress_tests`
 
 Stress tests depend from the Inference Engine Developer Package located in the
-`dldt` build directory.
+`openvino` build directory.
 
 In the command line snippet bellow, it is assumed that the Inference Engine
 Developer Package CMake module can be found in the directory `build` under
-`dldt` repository root.
+`openvino` repository root.
 
 ``` bash
 (
-export DLDT_BUILD_DIR=$(git rev-parse --show-toplevel)/build
+export OPENVINO_BUILD_DIR=$(git rev-parse --show-toplevel)/build
 mkdir -p build && cd build && \
-cmake -DInferenceEngineDeveloperPackage_DIR=$DLDT_BUILD_DIR .. && make -j$(nproc) \
+cmake -DInferenceEngineDeveloperPackage_DIR=$OPENVINO_BUILD_DIR .. && make -j$(nproc) \
 )
 ```
 
 ### Preparing Test Data
 
-Stress test use models from [Open Model Zoo][open_model_zoo]. Download and
-convert models to IRs using `./scripts/get_testdata.py` script.
+Stress tests may work with models from [Open Model Zoo][open_model_zoo]. To use it, 
+download and convert models to IRs using `./scripts/get_testdata.py` script.
+Script will update test config file with data required for OMZ models execution.
 
 From Intel network you can use models from cache at `vdp_tests` file share.
 Refer to [VDP shared folders][VDP-shared-folders] on using file shares.
 
 ### Running Tests
 
 ``` bash
-gtest-parallel ./MemCheckTests
+gtest-parallel <openvino_bin>/StressMemLeaksTests
 ```
 
+For MemCheckTests preferable way is:
 ``` bash
-gtest-parallel ./StressMemLeaksTests
-```
+python ./scripts/run_memcheck.py --gtest_parallel <gtest_parallel_py_path> 
+<openvino_bin>/MemCheckTests -- --test_conf=<test_conf_path> --refs_conf=<refs_conf_path>
+``` 
 
 MemCheckTests logs can be used to gather reference values based on current
 memory consumption: