Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Add edge bias feature to bias for testing edge cases. #515

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add edge bias feature to bias for testing edge cases. #515

wants to merge 1 commit into from

Conversation

matthew-russo
Copy link
Member

  • Works by randomly changing some generated values to be one of the random edge cases. The first tests are done with 100% edge cases, and then the chance goes down over the number of test cases until it's 0%.
  • The average amount of edge case tests can be controlled by edge_bias configuration option. It defaults to 0.25.
  • In failure the edge bias is persisted to the persistence file along with the seed, so it should be reproducible.
  • Also fix time::Duration test because the edge bias system found a problem in it. (Might need more modifications.)
  • Fix float_samplers test subsequent_splits_always_match_bounds.

replaces #369

@ajantti @matthew-russo
Add edge bias feature to bias for testing edge cases.
2fab3e3 
* Works by randomly changing some generated values to be one of the
  random edge cases. The first tests are done with 100% edge cases, and
  then the chance goes down over the number of test cases until it's 0%.
* The average amount of edge case tests can be controlled by edge_bias
  configuration option. It defaults to 0.25.
* In failure the edge bias is persisted to the persistence file along
  with the seed, so it should be reproducible.
* Also fix time::Duration test because the edge bias system found a
  problem in it. (Might need more modifications.)
* Fix float_samplers test subsequent_splits_always_match_bounds.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@matthew-russo @ajantti