Test ID Case Sensitivity Issue During Import
Describe the bug When importing tests, the test IDs are automatically converted to lowercase, causing discrepancies and errors. For instance, @ Sb2... becomes @ sb2 upon import, leading to issues in test identification and execution.
To Reproduce Steps to reproduce the behavior:
- Prepare a test file with test IDs in mixed case (e.g., @Sb2...).
- Import the test file into Testomat.
Expected behavior Test IDs should retain their original case, ensuring accurate identification and execution.
Screenshots
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
- Browser Version [e.g. 22]
- Application: [production or beta]
Additional context Add any other context about the problem here.
There is the following assumption:
If a number follows @S, the usual test is matched. If a symbol follows @S, the user test is not matched and the first S is displayed as lowercase s.
@BorshchOleksandr Thanks for the detailed info
Please try version 1.4.3 I have fixed
@testomatio/[email protected]
@DavertMik Thank you, your fix helped resolve the problem with 98% of the tests matching.
However, as I understand, there is still an issue as follows:
When we want to match tests for the second level of nesting, for example, Wallet, TimeLog, or Rise, you can look at our structure in the image.
In this case, the matching does not work based on the Test Suite ID.
I also noticed that after your last fix, everything in the test name after the parentheses is not considered (it gets cut off) and does not appear in Testomatio.
For example, this did not appear in Testomatio:
(e.g. [email protected]) (e.g. [email protected]) (e.g. test@)
etc.
@DavertMik have you seen the latest details?
Can you please say what framework did you use for catch this bug? Or maybe you can send example xml file with this bug please.
I check in few frameworks - maybe this bug was already fixed in last releases...
@BorshchOleksandr could you re-check this again? Does the issue still present?
Closing as done due to user's response.