Skip to content

mirage/factories: Use predictable values instead of random fake values #2127

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 15, 2020

Conversation

Turbo87
Copy link
Member

@Turbo87 Turbo87 commented Jan 14, 2020

This generally is easier to work with in my experience. If we want random values we can still generate them on a case-by-case basis, but by default we will have somewhat stable test fixtures now.

This should unblock #2120 :)

r? @locks

@locks
Copy link
Contributor

locks commented Jan 15, 2020

I agree with the above sentiment!
@bors r+

@bors
Copy link
Contributor

bors commented Jan 15, 2020

📌 Commit 3929db1 has been approved by locks

@bors
Copy link
Contributor

bors commented Jan 15, 2020

⌛ Testing commit 3929db1 with merge 5b1e23c...

bors added a commit that referenced this pull request Jan 15, 2020
mirage/factories: Use predictable values instead of random fake values

This generally is easier to work with in my experience. If we want random values we can still generate them on a case-by-case basis, but by default we will have somewhat stable test fixtures now.

This should unblock #2120 :)

r? @locks
@bors
Copy link
Contributor

bors commented Jan 15, 2020

☀️ Test successful - checks-travis
Approved by: locks
Pushing 5b1e23c to master...

@bors bors merged commit 3929db1 into rust-lang:master Jan 15, 2020
@Turbo87 Turbo87 deleted the faker branch March 30, 2020 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants