So in a unittest, does the assert method run something a lot of times?

I'm asking because in the video, we used the following:

self.assertGreaterEqual(int(self.hand3), 3)

and

self.assertLessEqual(int(self.hand3), 18)

But the thing is, we created the hands as follows:

self.hand1 = dice.Roll('1d2') self.hand3 = dice.Roll('3d6')

So let's say that hand 3 is a 2, 4, and 6 (when the hand is created). Now, you only have a single set of values, 2, 4, 6, and it asserts that this total is less than 19, and higher than 0. But what if you just got lucky? What if on 5% of cases, the hand created has a total value that is maybe a 5, 5, 12. Doesn't that specific case get missed, just because the hand created had a 95% chance of happening?

To put it simply: wouldn't it be possible for the code here to be faulty, but because it runs well 95% of the time, the hand created happened to be part of that 95%, and so the unit test assertion worked?

As I'm writing this, I'm actually starting to realize that maybe we will eventually cover the concept of running tests.py a million times, and that's how the statistics will get sorted out.

Still, since I'm not sure, I'm asking!

Thanks!