Friends of Eclipse,
Eclipse is an open source community that benefits millions of developers around the world each and every day! During the month of September, we are asking you to give back to our wonderful open source community. All donations will be used to improve Eclipse technology. Your contribution counts!
We thank you for this gesture, and for giving back to our community.
sse wtp 2.0 final test plan
sse wtp 2.0 final test plan
Proposed Plan (5.14.07)
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.
SSE API unit tests are in the org.eclipse.wst.sse.core.tests and org.eclipse.wst.sse.ui.tests plugins, located in the tests folder in the wst.sse component.
We do have several hundred unit tests which we expect to be running and passing for 2.0, which test various aspects of parsing, model creation, and correct charset handling, among other things.
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 they expected, even if it is working as designed.
As we progress through milestones, we'll add more and more detail for special cases, special files, special projects, etc.When we do have special or sample test files and projects, we will keep those stored in CVS, as projects under a testdata directory under the development directory of relevant component so that testers (from immediate team, or community) can easily check out into the environment being tested.
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.
We have added (some) automated performance tests along the
lines of the Eclipse base performance unit tests in future
milestones. These are currently in the
We will continue to add more test cases in upcoming milestones.
The following table represents the features for our various source editors that will play a role in our testing, according to the following legend.
|Structured Selection (expand selection to)||Y||Y||Y||Y||Y||Y||N||N|
|Open On (hyperlinks)||Y||Y||Y||Y||N||N||N||N|
|Find Element Occurrences (Occurrences in File)||Y||Y||Y||Y||N||N||N||Y|
|Delimiter Highlighting (bracket matching)||Y||Y||Y||Y||Y||Y||Y||P|
|Annotation Navigation (go to next annotation)||Y||Y||Y||Y||Y||Y||Y||Y|
|Quick Type Hierarchy View||N||N||N||N||N||N||N||N|
|Task Tags in Source Comments||Y||Y||Y||Y||Y||Y||N||Y|
A quick test of the Snippets View will be done, to be sure you can drop text, its inserted at right points, etc. and that users can define their own. There are many changes planned in this area, though, so we will test just enough to make sure it basically works, and does no harm (note: user defined ones in this milestone will most likely not be upwardly compatible with the next milestone).
Back to the top