if the assertion fails.
Here is an example:
::method test_addition
val = 2 + 3
self~assertSame(6, val, '2 plus 3 must equal 6')
and the output:
[failure] [20080701 09:19:45.455000]
Test: TEST_ADDITION
Class: STREAM.testGroup
File: C:\work.ooRexx\ooRexxUnit\3.2.0\ooRexx
On Tue, Jul 1, 2008 at 10:16 AM, Rick McGuire [EMAIL PROTECTED] wrote:
Mark, this has been wonderfulI think there's one more tutorial
piece needed, and that's how to write tests where you want to validate
that an error is generated.
Oh, yeah, you're right. Actually I also meant to show
Mark,
I was looking at what you've done for processing syntax errors in the
CONSTANT directive test group, and I have some suggestions that might
make these types of tests easier to manage. To start with, you can
completely eliminate the need to write this to a file by using the new
package
On Tue, Jul 1, 2008 at 11:29 AM, Rick McGuire [EMAIL PROTECTED] wrote:
I was looking at what you've done for processing syntax errors in the
CONSTANT directive test group, and I have some suggestions that might
make these types of tests easier to manage. To start with, you can
completely
It should still be available in the condition traceback information,
just like you're doing with assertion failures.
Rick
On Tue, Jul 1, 2008 at 4:40 PM, Mark Miesfeld [EMAIL PROTECTED] wrote:
On Tue, Jul 1, 2008 at 11:29 AM, Rick McGuire [EMAIL PROTECTED] wrote:
I was looking at what you've
Yes, that's one of the reasons I want executing code to have access to
it's own package. Once you have that, you can do things such as
dyamically add other packages to your lookup scope, perform dynamic
class resolution, etc. At lot of these functions will be particularly
useful from the native
