-
-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect Test Case Matching with Double Quotes #159
Comments
Info from chat on Discord Anker01 — 02/08/2023 18:25Hello , damies13 — 02/08/2023 19:13Thanks, I'll try to reproduce that damies13 — 02/08/2023 19:30OK found the issue, looks like I need to escape the double quotes as well
Try --help for usage information. vs
|
Confirmed the Double Quotes also need to be escaped on Window, but as I expected the |
…lies to all platforms not just Unix style platforms (MaxOS and Linux) Issue #159 should be resolved with this change
…3/rfswarm into Issue-#159-Double-Quotes
…3/rfswarm into Issue-#159-Double-Quotes
…3/rfswarm into Issue-#159-Double-Quotes
Merged into release branch v1.1.5 |
Describe the bug
When executing test cases with double quotes in the test case name using the Robot Framework, the test cases are not matched correctly, resulting in an error.
To Reproduce
Steps to reproduce the behavior:
Create a test case with double quotes in the name, like:
Test Case Send GET on API "${endpoint}" on "${env}" for "${tenant}" should be 200
Execute the following command:
$ robot -t "Send GET on API "${endpoint}" on "${env}" for "${tenant}" should be 200" "Anker01_variables.robot"
The test case is not matched correctly, and the output is as follows:
[ ERROR ] Suite 'Anker01 variables' contains no tests matching name 'Send GET on API ${endpoint} on ${env} for ${tenant} should be 200'.
Expected behavior
The test case should be matched and executed successfully.
Additional context
The issue seems to be related to how the Robot Framework handles escaped double quotes in the command for specifying test cases with double quotes in their names. Manually including escaped double quotes in the command allows the test case to be matched correctly and executed.
$ robot -t "Send GET on API "${endpoint}" on "${env}" for "${tenant}" should be 200" "Anker01_variables.robot"
This correctly identifies the test case and executes it, as seen in the output:
Send GET on API "my endpoint" on "QAENV" for "Anker02" should be 200 | PASS |
This bug affects users who need to work with test case names containing double quotes in their projects.
The text was updated successfully, but these errors were encountered: