assert: fix .throws and .doesNotThrow stack frames
All assert functions suppress their own function name from showing up in the stack trace.
That was not the case with throws
and doesNotThrow
.
On top of that I refactored two common.expectsError
cases that were less than ideal. I can open a new PR for that if that is requested, but I stumbled upon those when looking for a good place to add a new test, so I thought it would be fine to include it in this PR.
Checklist
-
make -j4 test
(UNIX), orvcbuild test
(Windows) passes -
tests and/or benchmarks are included -
documentation is changed or added -
commit message follows commit guidelines
Affected core subsystem(s)
assert, test