Recipe call arguments that name a data-driven column are not expanded, and the result depends on map order
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 58/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go
- 领域
- testing-qa
调研方向
Start in internal/runner/executor.go at runRecipeCall and resolve, then read the Data-driven page mentioned in the issue. Reproduce the issue with an Executor unit test using row values in e.vars and recipe arguments containing <email> and <password>. Done when recipe arguments are either expanded consistently before binding or the lint and documentation rule is made explicit, with behavior independent of map order.
由索引模型根据 Issue 内容生成。
描述
What happens
A recipe called from a data-driven test cannot reliably receive the row's columns as call arguments.
recipe "sign in as" (email, password)
type "<email>" into #email
type "<password>" into #password
test "role-based access"
sign in as "<email>" with "<password>"
with examples:
email password
"[email protected]" "admin123"
runRecipeCall binds each argument's text as it is (internal/runner/executor.go, the loop that calls setVar(param, args[i], ...)), so the parameter email is set to the text <email>. That replaces the row's email, and resolve then finds a variable whose value is its own placeholder and makes no progress: the step types <email> literally.
With parameter names that differ from the columns (recipe "sign in as" (address, secret)), the call binds address to the text <email>. resolve makes one pass over the variables in map order, so whether <address> becomes <email> and then the row's value depends on the order the pass visits address and email.
Measured
In a unit test on Executor (newTestExecutor, the row values set in e.vars, runRecipeCall with the arguments "<email>" and "<password>", then e.resolve("type <address> then <secret>")), 300 runs gave four different results:
type <email> then <password>: 179type [email protected] then <password>: 51type <email> then rowpw: 37type [email protected] then rowpw: 33
With the parameters named like the columns, the result is type <email> every time.
Expected
Either the arguments of a recipe call are expanded (against the row and the other variables) before they are bound, or probe lint and the docs say that a column must not be passed as an argument. The Data-driven page now says the latter, and shows a recipe without parameters that reads the columns directly; that form does not depend on the order.
Found while checking the recipe "log in as" example, which also had a keyword problem (fixed separately).
- 主要语言
- Go
- 星标
- 6
- 派生
- 3
- 平均合并
- 6 小时 28 分钟
- 30 天内合并 PR
- 362
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
AlphaWaveSystems/flutter-probe 的其他 Issue
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree order未关闭bug
难度 2/5 1-3 小时 新手友好度 76/100
AlphaWaveSystems/flutter-probe#865 ·
维护者通常 1 天内回复
-
area/cli bug
难度 2/5 1-3 小时 新手友好度 73/100
AlphaWaveSystems/flutter-probe#424 ·
维护者通常 1 天内回复
-
area/docs documentation
难度 2/5 1-3 小时 新手友好度 70/100
AlphaWaveSystems/flutter-probe#409 ·
维护者通常 1 天内回复
-
Dial timeout error should say how long it waited and name the timeout setting可能已有人在做 @jay23606 于 2 天前认领。 未关闭area/cli bug
难度 2/5 1-3 小时 新手友好度 78/100
AlphaWaveSystems/flutter-probe#408 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
AlphaWaveSystems/flutter-probe#888 ·
维护者通常 1 天内回复
查看 AlphaWaveSystems/flutter-probe 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
fluxcd/notification-controller#1441 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 66/100
volcengine/volcengine-go-sdk#163 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 76/100
OneBusAway/maglev#2145 ·
维护者通常 2 天内回复
-
priority/medium status/ready type/chore
难度 2/5 1-3 小时 新手友好度 84/100
discobox-ai/discobox#1357 ·
维护者通常 1 天内回复