Post
by krstcs » Mon Feb 13, 2017 4:27 pm
For the second situation, the verbiage is correct the way it is. It is talking about the test case not breaking, in terms of a software run break, not in terms of an error and something being broken (as in not working correctly). If you look at it from the point of view of the test case that you are setting the value for, then the test case should not break (as in it should not stop running the current iteration and start the next case or iteration), it should continue running the next module after the failed one in the current iteration.
Shortcuts usually aren't...