The Detached Status function allows the tester to detect tests that have been removed from the code for some reason. In testomat.io, they will be marked as “Detached.” This is a kind of synchronization, which allows you to keep tests up to date in TMS.
Import Tests From Source Code
In order to start testing in testomat.io, you must import existing tests from the framework into the TMS. To do this, use the Import Tests From Source Code function to select the desired settings (the framework and programming language), get the command, and paste it into the cmd in the queue file.
How Detached Status Works
If something changes in the code, you must re-import it to synchronize these changes with testomat.io. Tests that TMS did not find in the framework get the Detached label, and the user receives a notification: “Test was presumably deleted in the source code. Add it on next import or delete from the system”. That is, the tester realizes that there are tests in testomat.io that are not in the code, and their task is to figure out whether there really were changes in the project or tests were deleted by mistake.
If the tests have been deleted on purpose, they must be removed from the project in testomat.io. For this purpose, there is an option “Delete “Detached” tests” in the settings.
If an error has occurred and the tests need to be returned to the code, you should use the button “Clear “Detached” Status,” and all tests will resume in the database.
Benefits of Detached Status for Your Team
- ll information in testomat.io is always updated according to the code.
- The function insures users against irretrievable loss of information thanks to the possibility of restoring erroneously deleted tests.
- It helps to clear the project and delete irrelevant tests at the push of a button (Delete “Detached” tests).
Functions Related to Detached Status
- Out of sync test cases If the test in the code was not deleted completely but only changed, this information should also be updated in testomat.io. Such a test is marked as “Out of sync” and must be re-imported to update the data. In this case, Detached tests can be detected, and the tester will see that changes were made in the project and decide whether it is reasonable to save them.
- Sync automated tests by IDs In order to ensure that all changes made to testomat.io tests correlate correctly with the code, they are assigned identifiers (IDs), which are needed for internal communication between TMS and the framework. The function allows testomat.io to provide correct reports of test results and ensures proper CI/CD operation.
- Real-time reporting We use the TMS to monitor tests where they are stored in one place, and we can track their progress. When at least one test is completed, we can review the report to see changes in the system. Up-to-date information about tests that match the code is the key to properly reporting test results.
In addition to Real-time reporting, other features allow us to keep track of tests:
- Unlimited test results history This feature allows you to track the history of test changes in the Run Archive or Group Archive. It contains visualized information about when testing was performed and how many tests were passed, failed, or skipped. This allows the tester to clearly assess the area that needs maximum attention.
- Project Timeline or Pulse This function has a central place in the testomat.io project. And all tests imported from the code are arranged in chronological order. Pulse allows undoing all changes in test cases that were made in error.