Now that we're using ```seed``` before running these tests, I think ```assertCorrectPValue``` can be removed because the randomness has been removed from the observed output.

What this method did before was run the supplied function ```p_val_tests``` times and made sure that the observed output fell within ```exp_min``` and ```exp_max``` at least once. Since the output will always be the same due to seeding, we don't need to run the method multiple times; using ```assertFloatEqual``` should be fine instead.