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
eliminate
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
Hi Jeremy,
In the normal case the testing framework DO catch syntax errors and reports
them, but It can be tweaked for special tests. I only spotted this typo because
I saw it once, in a log file. This is how the test looks like (with the typo);
as you can see it is much more complex than “norm
On Sat, 22 Jul 2023, at 09:53, ooRexx wrote:
> I changed a typo “srip” to “strip" in the TRACE.testGroup with r12708
>
> - if t~lastItem~srip("l")~startsWith(">I> Method") then
> + if t~lastItem~strip("l")~startsWith(">I> Method") then
>
> Now many if not all platforms have a failure instead of j
