Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Recommendations for unit testing


Please take the lead on this since you are the WTP Test Automation focal point. Develop some guidelines and add them to the Web site. Thx.

Arthur Ryman,
Rational Desktop Tools Development

phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@xxxxxxx

"Daniel Somerfield" <dsomerfi@xxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

06/06/2005 02:14 PM

Please respond to
"General discussion of project-wide or architectural issues."

"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
[wtp-dev] Recommendations for unit testing

Hi all,
I am hoping to add some unit tests to the new cactus support in the JST, however it isn’t clear to me if there are standard practices (other than using junit) for testing WTP. I have looked at the testing documents on the site and browsed through some existing tests, but I could use a few pointers. The cactus code is highly dependant on the existence of the various Eclipse and WTP frameworks upon which it is built. Without that infrastructure, the tests will be pretty thin. For example, without an ICompilationUnit to adapt to a URL, you really don’t have much to test. Is there a strategy most of you use for situations like this? Any pointers would be appreciated. And if there is enough information I can aggregate into additional documentation, I would be happy to do so.
wtp-dev mailing list

Back to the top