main
Last updated
Last updated
Last updated: 2025-06-06 01:06:34.659013 File source:
This repository combines all tests and defines full testing pipeline of the platform. The test pipeline is rather complex and different stages are implemented in different repositories. This repository aims at holding all relevant information and definitions inrrespectively as well as provide the interface to test management framework, which displays results of each test run in the Gitlab CI pipeline.
There is a CLI that makes it easier to execute some functions of the test-suite locally. Please refer to the for more instructions.
code_quality
CI/CD Pipeline via GitLab Runners
implemented
unit_tests
CI/CD Pipeline via GitLab Runners
implemented
compliance_check
n/a
not implemented
n/a
integration_tests
Options: Local on devs machines & CI/CD Pipeline via GitLab Runners
implemented
security_tests
CI/CD Pipeline via GitLab Runners
implemented
End-to-end tests (also called functional_tests / e2e / feature)
Standalone Options: Local on devs machines & CI/CD Pipeline via GitLab Runners
implemented
End-to-end tests (also called functional_tests / e2e / feature)
Distributed Options: Local on devs machines & CI/CD Pipeline via GitLab Runners
implemented
integration_tests_live
live testnet (?)
not implemented
security_tests_live
live testnet (?)
not implemented
regression_tests
live testnet (?)
not implemented
performance_tests
live testnet (?)
not implemented
load_tests
live testnet (?)
not implemented
security_tests_3
live testnet (?)
not implemented
TBD
How to read the table: columns are environments and rows are test stages; there is a build
stage that is ommited and runs between pre-build tests and testnet environments:
y
means that a corresponding environment is needed to run a stage (equivalent -- a stage runs in that environment);
n
means the opposite -- a stage does not need that environment to run an is not executed in that environment;
The meaning of the testing matrix cells is explained below. Note, they may differ depending on the stage (e.g. manual execution of deploy stage means that at least part of the environment will need manual actions from community compute providers; likewise, manual acceptance tests consider involvement of beta testers). Furthermore, some test stages contain sub-stages and the whole matrix will be evolving together with the code base.
TBD: will define when and how we run advanced tests which need manual testing as well as heavy environments (we will not be able to run them very frequently, and that will need to be properly scheduled).
Local option: run make itest
in dms root; CI/CD pipeline
Local option: via as explained in ; CI/CD pipeline
Local option: via as explained in ; CI/CD pipeline
The branching strategy is defined .