jQuery Forum

You wouldn't change anything. It'd stop the test, not the module, not the suite. I'td be exactly what you're asking for without you writing a single extra line of code, which is actually less work for you than what you're asking for.

I see what you’re saying. Yes, it could just stop the test itself — throw an exception that was caught by the enclosing test() call. Maybe add a ‘fatal’ flag to equals, ok, etc.? Or create a fatal.equals(), etc. or fatalEquals()?

Everyone has their own comfort level for tradeoffs. For me, repeating code is to be avoided at a very strong level, while compatible changes to an API are at low level. For example, what if that was a < test in an ok() call, and at some point it needed to be chanted to <= — could you rely on people changing it in both places? Yes, I could move the expression out of the ok() (or equals()) entirely and put it in a boolean above and then check that in both places but that seems like a lot of work to avoid making painlessly available a value that is sitting right in the palm of qunit’s hand.

I did need similar functionality and took that step of storing the return value in a variable then testing the value of the variable.