I've had some trouble in the past explaining that expectedError is a testing fixture yet also causes the error to be "inverted" in the console output. That is: an example that should fail contains some expectedError declaration, and therefore outputs nothing. I think it's more intuitive that this marker is only treated as an inverting error in the testing framework, but leaves the console output alone for didactic purposes.
I've had some trouble in the past explaining that
expectedError
is a testing fixture yet also causes the error to be "inverted" in the console output. That is: an example that should fail contains someexpectedError
declaration, and therefore outputs nothing. I think it's more intuitive that this marker is only treated as an inverting error in the testing framework, but leaves the console output alone for didactic purposes.