Repository navigation
Fix the exported run command - #2004
Conversation
- Python, Ruby and JavaScript declare a reused test with a lowercase first letter, but run called it with the test's own case (Login() for a method named login). run now uses the same name. - JavaScript run awaits the reused test, which is async. - A test name from a variable is only known during playback, so run with one is exported as a comment that shows the variable, instead of a call to a method that doesn't exist. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
/agentic_review |
PR Summary by QodoFix exported run calls and handle variable test names
AI Description
Diagram
High-Level Assessment
Files changed (17)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can route each severity your way: inline, summary, both, or drop |
Description
runin Python, Ruby and JavaScript calls the reused test by the same name its method is declared with (first letter lowercase). Before,run | LogincalledLogin()while the method waslogin.runawaits the reused test (its method isasync).runwith a test name from a variable is exported as a comment, e.g.# Cannot export run with a test name from a variable: self.vars["runCMD"]. The name is only known during playback. Before, it called a method that doesn't exist (runCMD()).hasVariablehelper in side-code-export.Motivation and Context
tests/examples/simple-parent.sideusesrun | ${runCMD}. Every project intests/examplesstill exports to Python, Ruby and JavaScript that compiles.Types of changes
Checklist
🤖 Generated with Claude Code