Skip to Content

Changes for page Testing

Last modified by Pascal Robert on 2012/01/03 10:53
From version 17.1
edited by Ray Kiddy
on 2009/09/01 11:19
Change comment: adding ToC
To version 20.1
edited by Ray Kiddy
on 2009/09/03 11:22
Change comment: linkify the tool names

Summary

Details

Page properties
Content
... ... @@ -14,10 +14,10 @@
14 14  
15 15  Here are some relevant tools. It may be useful to search for their names in this wiki.
16 16  
17 -* Junit - for API testing
18 -* Selenium - for functional and some API testing
19 -* WOUnitTest - for functional testing (Is WOUnitTest current and being maintained? rrk)
20 -* JMeter - for performance testing
17 +* [[Junit]] for API testing
18 +* [[Selenium]] for functional and some API testing
19 +* [[WOUnitTest]] for functional testing (Is WOUnitTest current and being maintained? rrk)
20 +* [[JMeter]] for performance testing
21 21  
22 22  Questions still to be answered include the different approaches one must take to different kinds of applications. For example, testing a "regular" WOnder app may be different than testing a "DirectToWeb" app, which is also different than testing a Java Client or a "Web Services" application. Different application types make some things easier and some things harder. One may need different approaches or different tools. Also, one may be deploying an app as a regular java application, or as a servlet in a J2EE container (e.g. Tomcat) or the application may be managed in some other way. How an application is deployed may change how it needs to be tested.
23 23