feat(#511): scenario runner — capture step outputs into named variables#566
Merged
Timi16 merged 1 commit intoTimi16:mainfrom Mar 25, 2026
Merged
Conversation
… in scenario runner
Steps can now set `capture = "var_name"` to store their return value in a
named variable. Later steps reference captured values with `{{var_name}}`
syntax in their `args` or `expected_return` fields. An undefined variable
reference produces a clear error listing both the missing name and the
variables currently in scope.
|
@kehindefaith26 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
capturefield toScenarioStep: set it to a variable name and the step's return value is stored for reuse by later steps.{{var_name}}inargsorexpected_return.Changes
src/scenario.rs— newcapturefield,interpolate_variables()helper, variable accumulator inrun_scenario, 4 unit teststests/command_feature_tests.rs— 2 new integration tests (capture+interpolation success, undefined variable error)README.md— new### Scenario Commandsection with field reference table andcapture/{{var}}examplesTest plan
cargo testpasses (unit + integration)scenario_captures_step_output_and_uses_in_expected_returnpasses with counter fixturescenario_fails_on_undefined_variable_in_argsfails with clear error message containing the variable nameCloses #511