Lets use mock when possible but certainly Cactus is fine for when mock
won't suffice. Also, I suggest we focus on testing tomahawk for now
since we basically have a pretty decent test suite for the
implementation (the TCK tests.)
sean
On 9/22/05, Bill Dudney [EMAIL PROTECTED] wrote:
Hi All,
I believe that there is no problem for us in adding any dependencies
as long as they are ASL licensed...
If you would write up some stuff on how to get started with testing,
it would be great - I hope we can then get the other developers
(including me) to write those tests as well.
regards,
A few comments/questions on Bill's proposal...
The first is, do we want to go with Cactus, Cargo and Ant for this? I
don't have a problem with this although we've talked off and on about
using Maven for this at some point. Since our biggest Maven guru
(James Mitchell) is busy with some other
I posted this awhile back on the user list, but what about the
possibility of a testing renderkit? The encoding would write
values to a Map, and the decoding would read them from a Map.As
was pointed out before, it might not work with AJAX, but it'd
certainly simplify a great deal of the
Sounds like a great idea. What do you think Bill?
sean
On 9/22/05, Mike Kienenberger [EMAIL PROTECTED] wrote:
I posted this awhile back on the user list, but what about the
possibility of a testing renderkit? The encoding would write
values to a Map, and the decoding would read them from a
Hi All,
With the TCK behind us (thanks again to all who worked so hard on
that) I figured it was a good time to work on getting cactus tests in
place. My thinking behind Cactus is that we need to have the ability
to do in container testing because some of the mock stuff is just too
