Changes for page Testing
Last modified by Pascal Robert on 2012/01/03 10:53
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Parent
-
... ... @@ -1,0 +1,1 @@ 1 +How-tos - Content
-
... ... @@ -1,6 +1,6 @@ 1 -* [[||anchor="Approaches to Testing"]] 2 -* [[||anchor="Tools"]] 3 -* [[||anchor="Document Review"]] 1 +* [[#Approaches to Testing>>doc:||anchor="Approaches to Testing"]] 2 +* [[#Tools>>doc:||anchor="Tools"]] 3 +* [[#Document Review>>doc:||anchor="Document Review"]] 4 4 5 5 == Approaches to Testing == 6 6 ... ... @@ -14,12 +14,12 @@ 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 and TestNG - for testing of [[user applications>>Testing-JUnit and TestNG]] and for [[WOnder framework testing>>WOCOM :Project WOnder Frameworks JUnit Testing]]18 -* [[Selenium]] for both user and WOnder framework testing 19 -* [[WOUnit]] for unit and integration testing 20 -* [[WONDER :WOUnitTest]] for functional testing (Is WOUnitTest current and being maintained? rrk)21 -* [[WONDER :JMeter]] for performance testing22 -* [[Thrash Testing]] for testing threaded operations in EOF 17 +* Junit and TestNG - for testing of [[user applications>>doc:Testing-JUnit and TestNG]] and for [[WOnder framework testing>>doc:WOCOM.Project WOnder Frameworks JUnit Testing]] 18 +* [[doc:Selenium]] - for both user and WOnder framework testing 19 +* [[doc:WOUnit]] - for unit and integration testing 20 +* [[doc:WONDER.WOUnitTest]] - for functional testing (Is WOUnitTest current and being maintained? -rrk) 21 +* [[doc:WONDER.JMeter]] - for performance testing 22 +* [[doc: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 ... ... @@ -27,9 +27,9 @@ 27 27 28 28 There are many documents relevant to testing that should be evaluated for veracity, usefulness and relevance: 29 29 30 -* [[Testing-JUnit and TestNG>>Testing-JUnit and TestNG]] 31 -* [[Web Services-Testing Services with Terminal>>Web Services-Testing Services with Terminal]] 32 -* [[Web Applications-Development-Testing and JUnit>>Development-Testing and JUnit]] 33 -* [[Testing-Load Testing WO Apps with JMeter>>Testing-Load Testing WO Apps with JMeter]] 34 -* [[Testing-WOUnitTest>>WO :Testing-WOUnitTest]]35 -* [[Web Applications-Development-Testing and JUnit>>Development-Testing and JUnit]] 30 +* [[Testing-JUnit and TestNG>>doc:Testing-JUnit and TestNG]] 31 +* [[Web Services-Testing Services with Terminal>>doc:Web Services-Testing Services with Terminal]] 32 +* [[Web Applications-Development-Testing and JUnit>>doc:Development-Testing and JUnit]] 33 +* [[Testing-Load Testing WO Apps with JMeter>>doc:Testing-Load Testing WO Apps with JMeter]] 34 +* [[Testing-WOUnitTest>>doc:WO.Testing-WOUnitTest]] 35 +* [[Web Applications-Development-Testing and JUnit>>doc:Development-Testing and JUnit]]