Skip to Content

Changes for page Testing

Last modified by Pascal Robert on 2012/01/03 10:53
From version 46.1
edited by Ray Kiddy
on 2023/11/13 11:58
Change comment: Renamed back-links.
To version 45.1
edited by Ray Kiddy
on 2023/11/13 11:58
Change comment: Renamed back-links.

Summary

Details

Page properties
Content
... ... @@ -19,7 +19,7 @@
19 19  * [[doc:documentation.WOUnit]] - for unit and integration testing
20 20  * [[doc:WONDER.WOUnitTest]] - for functional testing (Is WOUnitTest current and being maintained? -rrk)
21 21  * [[doc:WONDER.JMeter]] - for performance testing
22 -* [[doc:documentation.Home.How-tos.Testing.Thrash Testing.WebHome]] - for testing threaded operations in EOF
22 +* [[doc:documentation.Thrash Testing]] - for testing threaded operations in EOF
23 23  
24 24  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.
25 25