-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
dryrun: keep track of loop variables from parent testsets
Partially fixes #27. The full fix might be to make `resolve!` also keep track of these loop variables; but this would involve storing lists of collected iterators for each nested testset: once we evaluate an iterator for filtering in `resolve!`, we have to store it in case it has some random behavior (e.g. `rand(1:9, i)` where `i` is a loop variable from a parent testset), in which case re-evaling it at execution time would lead to inconsistency. The testset tree would also have to be traversed depth-first by also unfolding testset-for. This could be a nice improvement if the perfs don't suffer (instead of storing parent strings subjects and looping through them, we would store iterators and recurse into them).
- Loading branch information
Showing
2 changed files
with
73 additions
and
14 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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