Sync automated tests by IDs

No need to manually mark automated scripts with IDs from Use developed importer to update all your tests in one click, check differences and merge changes into code repository

Automated tests synchronization code from git with test management tool

Synchronization automated tests by IDs functionality allows changes that occurred with tests in the test management system to correlate correctly with the code in the framework, for example, in Cucumber, but it might be any supported framework. IDs act as a kind of link between and your framework.

Why is test synchronization necessary?

To start working with test management you need to import existing tests from your automated testing framework into the test management system. This is possible thanks to the Advanced test importer from the source code after creating the project, just with a few clicks in the terminal.

But after import, the project does not stand still. Test project might be changed: feature files, scripts, steps, implementation tests, and other essential test case components. To keep all the information up to date, you need to do synchronization. And to ensure that all the changes made correctly correlate with the core code, you need IDs, which will pass data about the correspondence of tests in the code and TСMS.

To this end, we developed the concept of identifiers. They are assigned in to each test and suite and allow them to be equal to the code in the testing framework.

How Sync Automated Tests by IDs Works automatically assigns identifiers to all tests and suites. But they are not present in the project’s structure until you import them with an additional argument. To do this, go to the Import Automated Tests tab and select the Auto-assign IDs option. As a result of this query, all tests and suites IDs are imported into the project successfully.

There is also the inverse command that allows users to remove all previously assigned identifiers: -clean-ids- This option is relevant if you decide to continue working on the test project only in the framework, and it should no longer be synchronized with the test management system. When you use this command, you can delete IDs in the code; they will exist in as long as the project exists.

To know more detail, visit the following URL Import Automated tests from scratch in test management Docs.

Sync automated tests by IDs within CI\CD pipeline

Synchronizing autotests by ID is necessary for CI\CD to work correctly. Our TMS supports seamless integration with many CI\CD tools, enabling continuous testing and detailed reports of test results in real time and when they are completed. Thanks to Sync automated tests by identifiers (IDs) functionality, can correctly display testing results in reports.

Another feature set related to Sync automated tests by IDs:

  • Import automated tests – you can import any ready-made Unit, end-to-end, or API tests into test management, manage test runs and analyze their results. It is also possible to synchronize automated test cases with manual test cases in one place. Available importing tests into a specific branch or suite with keep the structure of source code too.
  • Keep Test IDs Between Projects – to import tests with Test IDs set in source code into another project use –create option. In this case, a new project will be populated with the same test IDs.
  • Detached Status – in test cases, you can not only make changes but also remove them from the code when they are not needed or by mistake. In this case, we can’t do without a kind of synchronization as well. Detached status functionality prevents test divergence between the testing framework and test management system. Its essence is that if a test is not found during the next import, it is marked as Detached. The QA engineer can verify changes in the project and either accept them or cancel the deletion.
  • Out-of-sync test cases – the Out of Sync function allows comparing the test scenario after modifying it with the previous imported version. If there is a discrepancy between them, the test scenario is marked as Out of Sync. To make the test scenario up-to-date, you need to import it again.