Reproducibility of results broken between Faker-0.7.18 and (Faker-0.8.0, 0.8.7)
See original GitHub issueFaker-0.8.0 and Faker-0.7.18 generate different values when given the same random
source.
Is the deterministic generation a goal of the project or not? I assumed that it is before… because the README specifically says that it’s useful for unit testing, which is how I use it.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:23 (5 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think it’s fine to use semver, just add a notice that the data inside the providers is subject to change between versions, and that the only guarantee of reproducibility is when using the same faker version.
@sp-1234 Since we keep updating data in the providers pretty much at every release, we’ll keep breaking the reproducibility at every release.
Maybe we should just stop using semver entirely and switch to date-based versioning.