
162 Model-Based Testing for Embedded Systems
captures most of the behavior of the Set<E> interface. One of the two mutants that were
not detected is in the iterator() method, which we did not test in our model. The other
mutant indicates that we are not testing the case where the argument to the equals method
is a different type of object (not a set). This is a low-priority case that could be ignored or
could easily be covered by a manually written JUnit test.
6.6.5 Testing with large amounts of data
What if we wanted to do some performance testing to test that sets can handle hundreds or
thousands of elements? For example, we might know that a SUT lik ...