I did mean the latter. I was hoping to
expose cactus testing capability to the end-user. If this is not something that
fits within the scope of WTP, then perhaps there is some other, more
appropriate home for it. It certainly is going to depend on WTP and Eclipse
JUnit integration. I suppose there isn’t really a standard per-se for testing
of server-side components.
Thanks for your thoughts.
Dan
From:
wtp-dev-admin@xxxxxxxxxxx [mailto:wtp-dev-admin@xxxxxxxxxxx] On Behalf Of Michael Elder
Sent: Thursday, March 10, 2005
12:30 PM
To: wtp-dev@xxxxxxxxxxx
Subject: Re: [wtp-dev] WTP and
Server-side testing
Can you clarify if you
mean using Cactus tests to drive some of our server tooling test scenarios, or
providing tooling for end-users to run cactus tests?
If you mean the
former, then that's really cool and you can ignore the rest of my comments. If
you mean the latter, then it may not be within the scope of the WTP project
scope. The Web Tools Platform is meant to provide tooling only for standards,
and while the Jakarta/Apache Cactus project is a great thing, and perhaps a de
facto standard, I don't think it falls within the boundaries of our scope.
Does anyone else have
any thoughts on this?
-------------------------------------------------------------------------
Rational Studio / J2EE Tools Development
Thursday,
March 10, 2005 3:17 PM
To: wtp-dev@xxxxxxxxxxx
cc:
From: Jeffrey Liu <jeffliu@xxxxxxxxxx>
Subject: Re: [wtp-dev] WTP and Server-side testing
Hi Dan,
Welcome
on board. Our goal is to automate as much testing as possible using JUnit.
Right now, we are running these JUnits through the Eclipse testing framework,
which support some level of server-side testing (if by server-side you mean the
Eclipse workbench). If by server-side you mean testing J2EE container code such
as servlet and EJB, I don't think we have any of these tests yet. Even if we
do, the number is very limited.
I'm
not very familiar with Cactus myself, but I'm very interested to see it in
action. AFAIK, Cactus builds around JUnit, so if the need is there, I can't
think of a reason why we don't want to use it. Maybe we can chat offline and
discuss the specifics.
Thanks,
Jeffrey Liu
IBM Rational Software - Performance Analyst
IBM Toronto Lab.
8200 Warden Ave. Markham, Ontario, L6G 1C7
Internal mail: D3/R8V/8200/MKM (D3-268)
T/L: 969 3531
Tel: (905) 413 3531
Fax: (905) 413 4920
jeffliu@xxxxxxxxxx
"Daniel Somerfield"
<dsomerfi@xxxxxxx>
Sent
by: wtp-dev-admin@xxxxxxxxxxx
03/10/2005 01:43 PM
Please
respond to
wtp-dev
|
|
To
|
<wtp-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
|
[wtp-dev] WTP and Server-side testing
|
|
Hi everyone,
Following
Konstantin’s lead, I would also like to say a quick hello. I am a
co-worker of his at BEA and work on the debugger side of things. I am hoping to
be able to contribute in the area of debugging and testing.
Speaking
of which, I have a question about what, if any plans, there are to support
server-side component testing (such as cactus tests)? I have cobbled together a
cactus launch short-cut that I would be happy to contribute to WTP. Right now I
use a couple of internal packages that I probably shouldn’t, both in junit
and wst. I would love to advice for how to clean it up so I am not abusing the
API-usage conventions.
Is
cactus something of interest or is there something else in the works for
testing? I would be happy to chat either on the mailing list or off-line if
there are other interested parties.
Thanks
very much and it is nice to meet you all,
Dan