Fix seeding for generative policy tests #1508
Merged
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.
We are seeding the
testRand
module level variable. However, testing/quick was not set to use that seeded random number generator. The testing/quick configuration has a fieldRand
which is not set, will result in a random number generator being created and used. This created generator hasn't been seeded so our seeding had no impact on any of ourGenerate
functions.This commit updates all testing/quick tests to initialize
Rand
in the configuration to be set to our seededtestRand
.Signed-off-by: Sean T. Allen seanallen@microsoft.com