Open mrogachenko-cg opened 2 months ago
Known issue.
We can't detect that multi-word parameter matches the test, so let's say if we have two tests:
User clicks link to login
User #{param}
If we allow param to contain whitespaces, receiving report for User clicks link to login
we can match User #{param}
instead.
This is why we would like to ask to use camelCase or underscore_case (underscore chars are ok as params).
@DavertMik I'm sorry, it's not quite clear why you need to detect test case matching by multi-word parameters instead of matching it by provided test case id? Not sure that current issue is the same you've mentioning.
re-opened per user request
Describe the bug When parametrized test have a parameter value with whitespace (e.g. "some value") are registered in test run, all of them are grouped as the same test with 'retry', while it is expected to be registered as separate test (separate execution line).
Prerequisites
To Reproduce Steps to reproduce the behavior:
Expected behavior Each test execution should be registered as separate run
Actual behavior For single word parameter it is working as expected, for multy-word parameter it is registered as 'retry' for the same test with 'empty' parameters value
Screenshots
Additional context Probably another characters (not only [whitespace] may trigger the same problem)