Skip to Content

Changes for page Testing

Last modified by Pascal Robert on 2012/01/03 10:53
From version 26.1
edited by Ray Kiddy
on 2009/09/01 11:14
Change comment: hopefully this will become a 'Best Practices' page. We will see.
To version 27.1
edited by Greg.Brown
on 2009/09/26 15:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.kiddyr
1 +XWiki.gbrown
Content
... ... @@ -1,3 +1,7 @@
1 +* [[||anchor="Approaches to Testing"]]
2 +* [[||anchor="Tools"]]
3 +* [[||anchor="Document Review"]]
4 +
1 1  == Approaches to Testing ==
2 2  
3 3  There are different kinds of tests and different approaches to testing. No one technology or approach will work for everyone. These are some of the relevant technologies and issues in testing WebObjects and WOnder applications and frameworks.
... ... @@ -10,10 +10,10 @@
10 10  
11 11  Here are some relevant tools. It may be useful to search for their names in this wiki.
12 12  
13 -* Junit - for API testing
14 -* Selenium - for functional and some API testing
15 -* WOUnitTest - for functional testing (Is WOUnitTest current and being maintained? rrk)
16 -* JMeter - for performance testing
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
17 17  
18 18  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.
19 19  
... ... @@ -21,16 +21,9 @@
21 21  
22 22  There are many documents relevant to testing that should be evaluated for veracity, usefulness and relevance:
23 23  
24 -* [[Project WONDER-Frameworks-ERSelenium>>WO:Project WONDER-Frameworks-ERSelenium]]
25 -* [[Selenium Introduction]]
28 +* [[Testing-JUnit and TestNG>>WO:Testing-JUnit and TestNG]]
26 26  * [[Web Services-Testing Services with Terminal>>WO:Web Services-Testing Services with Terminal]]
27 27  * [[Web Applications-Development-Testing and JUnit>>WO:Web Applications-Development-Testing and JUnit]]
28 -* [[How to Develop Selenium Tests]]
29 29  * [[Testing-Load Testing WO Apps with JMeter>>WO:Testing-Load Testing WO Apps with JMeter]]
30 -* [[Testing-JUnit>>WO:Testing-JUnit]]
31 31  * [[Testing-WOUnitTest>>WO:Testing-WOUnitTest]]
32 -* [[How to test a Diva app with Selenium>>WO:How to test a Diva app with Selenium]]
33 -* [[Web Services-Testing Services with TerminalWO:Web Services-Testing Services with Terminal]]
34 -* [[Specifying Robust Selenium Element Locators]]
35 35  * [[Web Applications-Development-Testing and JUnit>>WO:Web Applications-Development-Testing and JUnit]]
36 -* [[Project WOnder Frameworks JUnit Testing]]