Guidance on UNIT tests , integrations tests and git workflow

[Shridhar-2205]

Unit or Integrations tests in SLIM repo are scattered and unclear for controlplane and dataplane, I see some tests here: https://github.com/agntcy/slim/tree/main/tests and some here:https://github.com/agntcy/slim/tree/main/data-plane/python-bindings/tests, not sure which tests are run as part of git workflow. Need guidance on that.

[janosSarusiKis]

We generally use task files to execute tests, with GitHub (GH) workflows invoking each task command.

This project is multi-module and multi-language, allowing each component to define its own tests within its scope.

The workflow defined in integration-tests.yaml runs tests located in the tests directory. The final step of the integration-test job is to execute the task tests:integration, which aims to validate the entire ecosystem.

For the control-plane, unit tests are written in Go to test the nodecontrol package. These tests are run via a GH workflow that uses a task file, as seen in reusable-go-build-and-test.yaml#L102. This workflow is triggered on each pull request by the control-plane.yamlworkflow.

Data-plane specific tests, located in data-plane/python-bindings/tests, are executed by the GH workflow defined in reusable-python-build-and-test.yaml#L67.

Please reach out if you need further clarification and if want to add test to the code feel free to open a PR/issue.