Use create_ticks() outside of benchmark for improved code coverage

This commit is contained in:
Greg Fitzgerald 2018-02-16 09:06:25 -07:00
parent 2a04f4b52a
commit 09ccc1ee6d
1 changed files with 5 additions and 8 deletions

View File

@ -107,14 +107,11 @@ mod tests {
assert!(verify_slice(&vec![], 0)); // base case
assert!(verify_slice(&vec![Event::new_tick(0, 0)], 0)); // singleton case 1
assert!(!verify_slice(&vec![Event::new_tick(0, 0)], 1)); // singleton case 2, bad
assert!(verify_slice(
&vec![Event::new_tick(0, 0), next_tick(0, 0)],
0
)); // lazy inductive case
assert!(!verify_slice(
&vec![Event::new_tick(0, 0), next_tick(1, 0)],
0
)); // lazy inductive case, bad
assert!(verify_slice(&create_ticks(0, 0, 2), 0)); // inductive case
let mut bad_ticks = create_ticks(0, 0, 2);
bad_ticks[1].end_hash = 1;
assert!(!verify_slice(&bad_ticks, 0)); // inductive case, bad
}
}