The problem with the original line is that because of the reply statement, the error did not get propagated back to the calling framework, it just terminated the thread. Because that did not get trapped and there were no assertion failures, it was marked as successful. Correcting the typo eliminated the error, which caused the assertion failure. From the assertion information, it's obvious that the method activation line in the trace did not get removed, which caused the mismatch on the assertion.
Rick On Sat, Jul 22, 2023 at 9:38 AM Jeremy Nicoll <jn.ml.sfrg...@letterboxes.org> wrote: > On Sat, 22 Jul 2023, at 14:14, ooRexx wrote: > > Hi Jeremy, > > > > In the normal case the testing framework DO catch syntax errors and > > reports them, but It can be tweaked for special tests.... > > That's fascinating. I didn't stop to think about how one would design a > framework intended to spot errors in ooREXX's internal error handling > which - I think - is what you're saying this error occurred in? > > -- > Jeremy Nicoll - my opinions are my own. > > > _______________________________________________ > Oorexx-devel mailing list > Oorexx-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/oorexx-devel >
_______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
