Seamless integration provides that automated tests are always up to date from each new import. If you make changes to early imported tests in the test management system, those tests will be marked as out-of-sync. So, Keep abreast of all your tests with testomat.io
Update the automatic tests after each new import, keep track of any changes made, and cancel them if necessary.
How Out of Sync Test Cases Function Is Useful for Your Team
As soon as you import your tests into testomat.io, many new features open up for you. You will be able to track your tests instantly and effortlessly. The system will record every change you make and warn you if the content differs from the version you imported from the source code. Such a test is called an unsynchronized test.
There must be a match between the test in testomat.io and the source code written by the tester. For example, a test is imported and modified in testomat.io. Then, when you run the local code through the terminal, you will get a non-true correct result. That is, an old version of the code will be run while a new version is needed.
With this feature, you can see which automated tests were changed and when, view unsynchronized content, and compare the previous and current versions. This allows you to make timely decisions about updating source code and re-importing or undoing earlier changes.
How To Use Out of Sync Test Cases
This is a separate tab on the Tests page that applies to automated tests. Content that differs from the source code is marked as out of sync tag.
You can not only view changes and code but also compare recent versions (Compare Description), see the history of all changes (History), and edit content (Edit).
How to compare content versions?
By clicking on Compare Description, you get access to the current and previous versions of the content (Diff for test).
For example, the draft of a script may be different from the script code. In this case, you will see how the scenario is implemented in the code (Scenario Code) and how it was written in testomat.io (Scenario Description). The source code is used as a source of truth, meaning you must either update the script or undo the changes (Reject description).
You can view all existing versions with the date and time of change on the History tab. Navigate to any of them to compare with the previous or with the current version, as well as to return to the previous version.
After comparing versions, you’ll have an easier time deciding if you need to edit the content.
How to edit a test?
The editor (Edit Test) allows you to make changes and track them. This is especially useful when a large team is working on the same project. If necessary, you can undo changes if they are wrong or go back to a previous version.
If these are classical tests and not BDD, there is no possibility of changing the code. But you can make a description through Edit and show it to the automation specialist.
- Versioning – version comparison allows you to understand what changes have been made to the content. Typically, the previous and next versions are compared, but it is possible to compare any selected version to the current one. This is an essential part of working with changes.
- Import Automated – tests If you already have tests (end-to-end, API, modular), import them into testomat.io. In the system, they will be marked as “automated” by default. After each import, you can update tests, track changes, and cancel them if necessary.
- History – the history displays all the available versions with the date and time. You can use this feature while working with Out of sync test cases to make it easier to decide if you need to update your code or undo changes.
- BDD Support – the testomat.io solution supports BDD tests. This allows you to involve team members without technical experience in automated testing, including tracking Out of sync test cases and working with changes.
- Add Classical Test Case – in addition to BDD, testomat.io supports classical tests. In this case, when working with Out of sync test cases, it is not possible to change the code yourself, but it is possible to create appropriate descriptions for automators.