Skip to content

Dependencies Matrix

Jump to bottom
Sandra María Castro edited this page Jan 26, 2026 · 4 revisions

The VIPER core dependencies tree

VIPER_Dependency_tree

TestVIPER Stages and their Dependencies

Main Branch

TestVIPER will monitor the health of the components in their main branches. Existing integration tests in the testviper repository are executed in this stage and expected to pass.

Feature development is expected to happen in feature branches and merge to the develop branch that itself will be merged to main at a later stage determined by the development cycle.

TestVIPER will dispatch the execution of integration tests on the event of merges to the main branches of the relevant components.

Staging - Develop Branch

Feature development happens on feature branches created off the develop branch. TestVIPER will dispatch the execution of integration tests on the event of merges to the develop branch of the relevant components.

New features may need new integration tests or updates to existing ones and this development work will happen in features branches of TestViper. In a similar way, TestVIPER will have a Develop branch (aka Integration branch) to execute the code available in the Develop branches of the components.

  • Execute unit and component tests of VIPER components on pushes to the develop branches
  • Test results and reports are publised to the Allure Reports in the Staging channel. (TBD).

Clone this wiki locally