Set random.seed
explicitly in each test function for rest streaming
#689
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: process
A process-related concern. May include testing, release, or the like.
Currently, the tests for rest streaming depend on a single seed value configured globally within the file here. This makes the tests non-deterministic and inter-dependent making it difficult to understand and debug test failures.
Instead, we can either:
random.seed
explicitly in each test function. The value can either be hard-coded in (recommended), or it can be varying (by passing in, say, an integer based on time of day, PID, etc.) .or
_ResponseItr
within the test file.In either case, make sure the logs and / or errors print out what the value of the seed turned out to be, so that if we encounter the same failure, we can make sure the test function sets the same seed so we can replicate it.
Also do the same for the test cases of asynchronous rest streaming once implemented. See: [async rest]streaming(#686)
Reference: #686 (comment)
The text was updated successfully, but these errors were encountered: