testomatio
Importing automated tests with the --update-ids option automatically creates test suites within the parent suite
Describe the bug
Importing automated tests with the --update-ids option automatically creates test suites within the parent suite.
To Reproduce Steps to reproduce the behavior:
- Create a describe with nested describes
- Import automated tests with the
--update-idsoption - Check the automatically created suites in the parent suite
Expected behavior All test cases after sync should exist within one test suite, the same order they were created
Screenshots
Desktop (please complete the following information):
- OS: macOS
- Browser Firefox
- Browser Version 131.0.3 (aarch64)
- Application: production
@AZANIR can you fix this? @DavertMik is there any backend to be fixed here?
A version with a fix for this problem has been released today, check if everything is working properly for you.
https://github.com/testomatio/reporter/releases/tag/1.6.16
If it doesn't work for you, please provide a project structure without data, also indicate which framework you are using. and what your framework is based on (programming language)
related to testomatio/check-tests#198
Rechecked — issue is still valid
We’ve re-verified this behavior using a CodeceptJS + TypeScript project. When multiple Feature() blocks (or nested describe structures) are defined in a single file, importing with --update-ids still creates child suites inside the parent instead of keeping all tests under one suite.
Environment: @testomatio/check-tests v0.11.1, @testomatio/reporter v2.3.6, Node.js v22.20.0, Windows 11.
Result: Bug is still reproducible on the latest versions — additional child suites are automatically created within the parent suite.