Mark, you have provided a lot of material on unit testing
and I thank you for it. It has definitely clarified a number
of points that I was wondering about.
I have started on STREAM, but am going to have to take
a couple of days to repair another PC that just failed.
Luckly things only happen in
Rick pointed out that I forgot to include how to do negative tests.
This is really an important part of testing, and since I spent a lot
of time in test, I'm kicking myself for overlooking it here.
We'll continue with the STREAM.testGroup and look at what the doc says
about the second arg. Whi
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 sh
And I will vote in favor of them
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.
Rick
On Tue, Jul 1, 2008 at 12:52 PM, Mark Miesfeld <[EMAIL PROTECTED]> wrote:
> What are the as
What are the assertXXX() methods. The last in this series for a bit.
After reading the other posts in this series, the main thing that is
left is to list the different assertXXX() methods.
They are:
assertEquals(expected, actual, )
assertNotEquals(expected, actual, )
assertNull(actual, )
ass
Picking up with writing the new test group STREAM.testGroup.
The last post showed the top boilerplate from the the template file.
This picks up the actual test case class. I'm not to going to explain
too much about the class part of this, I'll save that for later. This
is about just editing the
Starting a new test group. I'm going to assume that the reader has
been following along in the thread and try not to repeat myself.
The idea behind this thread is to show how to start writing test cases
even if you do not understand classes by using boilerplate code.
If you download the 02 snaps
I just did a quick scan of the test cases, and it's pretty easy to
find holes in the coverage. Here's what I found in less than 5
minutes of searching:
There's no coverage for the "multiple condition" forms of IF, WHEN,
WHILE, or UNTIL (e.g. "if a = 1, b = 2 then "
There are no select tests t
I'm going to continue this thread on how to write a test case in a
series of posts. Hopefully one day I will then transfer the content
to the Wiki.
First, a little info on contributing to the project / to the test suite.
The test suite is enormously helpful to the project. Everyone and any
one
Bill, and any others,
This is a continuation from where I left off in the ooRexxUnit 3.2.0
Snapshot 02 thread.
We looked at this, which I said was the heart of a test case:
::method "test_MULTIPLE_INHERITANCE_WITH_MULTIPLE_METACLASSES"
self~assertEquals("'123.'", .class123~info)
So, let's wr
10 matches
Mail list logo
