Import into branch

You are free to work with the separated branch, like with git branches. Import tests into this specific branch if a branch parameter is used.

Test Management feature Import test cases into a branch

Nowadays, branching strategy is an essential part of software development. Branch mention, we mean Git branching flow as the most known workflow. Due to the test management system – the version control approach can be used not just for control of development as well for maintaining the testing process. And from now you can create multiple versions of tests in branches. Our team implemented this functionality to improve collaboration within the Agile team.

Note, that these test management branches are independent branches. These branches have nothing in common, apart from the context with Git branches. QA engineers are free in context determining.

How branching works in test management

You are free to create new branches, manage active and merge existing ones through Branch Menu on the test management app Dashboard. Also, the built-in tags and labels will always show the branch you work are. Find out more details about @Tag functionality in our test management solution by following the link.

Types of tests you might manage with branches:

  • automated tests
  • manual test cases
  • BDD test cases

Import automated tests into branch of the testing project

Tests can be imported into a specific branch via TESTOMATIO_BRANCH parameter of the command-line interface (CLI). The branch is matched by its id. If one will not found, it will be created automatically. Learn this configuration automated test import on Docs.

Advantages Git branching strategies for test automation framework

  1. Creating a new branch initiate experiments and discussions around a branch within the QA team that facilitates improving their collaboration.
  2. Branch concept makes testing delivery faster because QA engineers may work independently without disturbing the main stable branch. After then merge their results in the main branch.
  3. So, each of the features you may place in a dedicated branch instead of the common branch. Make decomposition into branches by testing type: regression testing, smoke testing or API testing etc.
  4. The main branch will never contain irrelevant tests, which is a huge advantage for CI\CD environments.
  5. Branching flow helps a lot in the maintenance of scalable test projects through task optimization.