bazel: unfied test suites

add common test suites across repositories

Author: PiotrKorkus

BUILD

@@ -104,3 +104,21 @@ test_suite(
     tests = ["//src/cpp/tests:bm_kvs_cpp"],
     visibility = ["//visibility:public"],
 )
+
+test_suite(
+    name = "unit_tests",
+    tests = [
+        "test_kvs_cpp",
+        "//src/rust/rust_kvs:tests",
+    ],
+    visibility = ["//visibility:public"],
+)
+
+test_suite(
+    name = "cit_tests",
+    tests = [
+        "//tests/python_test_cases:cit_cpp",
+        "//tests/python_test_cases:cit_rust",
+    ],
+    visibility = ["//visibility:public"],
+)

tests/README.md

@@ -67,6 +67,26 @@ pytest -v . --build-scenarios --self-contained-html --html report.html --traces
 > Traces are collected using `stdout`.
 > Setting `--capture` flag (including `-s`) might cause traces to be missing from HTML report.
 
+### Bazel execution
+
+Run all Component Integration Tests:
+
+```bash
+bazel test //:cit_tests
+```
+
+When the dependencies in [requirements.txt](python_test_cases/requirements.txt) file are manually modified, the user should invoke command and commit changes:
+
+```bash
+bazel run //tests/python_test_cases:requirements.update
+```
+
+In order to update all dependencies use:
+
+```bash
+bazel run //tests/python_test_cases:requirements.update -- --upgrade
+```
+
 ## Standalone execution of test scenarios
 
 Test scenarios can be run independently from `pytest`.

tests/python_test_cases/requirements.txt

@@ -1,4 +1,3 @@
-# Fully resolved list of dependencies is required by Bazel.
 psutil
 pytest-metadata
 pytest-env