| <?xml version="1.0" encoding="UTF-8"?> |
| <?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?> |
| <html> |
| <head> |
| <meta name="root" content="../../../../../" /> |
| <title>WST Command Component Milestone 5 test plan</title> |
| </head> |
| |
| <body> |
| <h1>WST Command Component Milestone 5 Test plan</h1> |
| |
| <h2>Status of this Plan</h2> |
| <p>Proposed Plan (06-16-2005)</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> |
| We don't have any official API yet |
| but will reserve this space for |
| future plans to details where API Unit tests are, their |
| coverage, etc. |
| </p> |
| |
| <h3> |
| <b>End User Testing</b> |
| </h3> |
| <p> |
| The testing of the Evironment Command Framework and Dynamic Wizard Framework |
| will be done by testing the plugins that uses these frameworks. |
| </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. |
| </p> |
| |
| <h3> |
| <b>Performance Testing</b> |
| </h3> |
| <p> |
| We have added some automated performance test cases. |
| We will continue to add more test cases in upcoming |
| milestones. |
| </p> |
| <br /> |
| <h2>Test scenarios</h2> |
| <br /> |
| <p> |
| The testing of the WST Command component will be covered by |
| the |
| <a href="../../../../jst/components/ws/M5/test_plan.html"> |
| JST Web Services Tools Milestone 5 Test Plan |
| </a> |
| . |
| </p> |
| |
| </body> |
| </html> |
