Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Setrandom.seed explicitly in each test function for rest streaming #689

Open
Assignees
ohmayr
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.type: processA process-related concern. May include testing, release, or the like.
@ohmayr

Description

@ohmayr

Currently, the tests for rest streaming depend on a single seed value configured globally within the filehere. This makes the tests non-deterministic and inter-dependent making it difficult to understand and debug test failures.

Instead, we can either:

  • setrandom.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

  • pass in the seed to the constructor of_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)

Metadata

Metadata

Assignees

Labels

priority: p2Moderately-important priority. Fix may not be included in next release.type: processA process-related concern. May include testing, release, or the like.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions


    [8]ページ先頭

    ©2009-2025 Movatter.jp