Skip to Content

Changes for page Testing

Last modified by Pascal Robert on 2012/01/03 10:53
From version 28.1
edited by Greg.Brown
on 2009/09/26 15:57
Change comment: There is no comment for this version
To version 37.1
edited by Ray Kiddy
on 2009/11/03 11:26
Change comment: add link to new thrash testing page

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.gbrown
1 +XWiki.kiddyr
Content
... ... @@ -15,9 +15,10 @@
15 15  Here are some relevant tools. It may be useful to search for their names in this wiki.
16 16  
17 17  * Junit and TestNG - for testing of [[user applications>>WO:Testing-JUnit and TestNG]] and for [[WOnder framework testing>>Project WOnder Frameworks JUnit Testing]]
18 -* [[Selenium]] for both user and WOnder framework testing
19 -* [[WOUnitTest]] for functional testing (Is WOUnitTest current and being maintained? rrk)
20 -* [[JMeter]] for performance testing
18 +* [[Selenium]] - for both user and WOnder framework testing
19 +* [[WOUnitTest]] - for functional testing (Is WOUnitTest current and being maintained? rrk)
20 +* [[JMeter]] - for performance testing
21 +* [[Thrash Testing]] - for testing threaded operations in EOF
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