| <?xml version="1.0" encoding="utf-8"?> |
| <?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?> |
| <html> |
| <head> |
| <meta name="root" content="../../../www/" /> |
| <title>WTP Server Tools 2.0 final test plan</title> |
| </head> |
| <body> |
| <h1>WTP Server Tools 2.0 final test plan</h1> |
| <h2>Status of this Plan</h2> |
| <p>Proposed Plan (6.18.07)</p> |
| |
| <h2>Overall goals</h2> |
| <h3> |
| <b>Co-developer Testing</b> |
| </h3> |
| <p> |
| We will inspect "runtime" version of build to be |
| sure extra source is not included, and more important, we'll |
| inspect and test importing SDK version to be sure all |
| relevant "open source" is included in that SDK |
| build and that it correctly imports into a development |
| environment. |
| </p> |
| <h3> |
| <b>API Testing</b> |
| </h3> |
| <p> |
| Server tools API is tested through several plugins, located in the |
| <i>tests</i> folder in the wst.server and jst.server component. |
| </p> |
| <p> |
| We have several hundred unit tests which we expect to be |
| running and passing for 2.0, which test various aspects of |
| server creation, server adapters, UI, and |
| other things. |
| </p> |
| |
| <h3> |
| <b>End User Testing</b> |
| </h3> |
| <p> |
| The nature of the end-user testing is intentionally planned |
| to be "ad hoc" instead of specifying step by step "how to" |
| directions and specific "expected results" sections often |
| seen in test cases. This is done because its felt leads to |
| greater number of "paths" being tested, and allows end-users |
| more motivation for logging "bugs" if things didn't work as |
| <i>they</i> expected, even if it is working as designed. |
| </p> |
| |
| <h3> |
| <b>Platform Testing</b> |
| </h3> |
| <p> |
| While we do not have any platform specific code, or |
| function, we will have some team members do end-user tests |
| on Linux, some on Windows. We will also confirm unit tests |
| pass on both platforms. |
| </p> |
| |
| <h3> |
| <b>Performance Testing</b> |
| </h3> |
| <p> |
| We have added (some) automated performance tests along the |
| lines of the Eclipse base performance unit tests in future |
| milestones. These are the "tests.performance" plugins in the |
| tests folders in CVS highlighted above. |
| </p> |
| |
| <h3> |
| <b>Adopter usage</b> |
| </h3> |
| <p> |
| We have several adopters who depend on server tools for |
| everything from server tools API to UI to providing additional |
| server adapters. We'll poll several adopters to ensure that |
| they are testing on recent builds and adjust our testing to |
| ensure coverage of all areas or areas that are heavily used. |
| </p> |
| </body> |
| </html> |
