Status of this 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.
Here in 2.0 we don't consider we have any official API yet (since not spec'd as such) but will reserve this space for future plans to details were API Unit tests are, their coverage, etc.
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.
End User Testing
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.
Testing focus for 2.0
- Verify quick fix for spelling mistakes works
Syntax highlighting preferences:
- Verify font styles (bold, italics, strikethrough, etc) are obeyed
- Verify background syntax color preference is followed
- Verify keywords for preference pages works
- Verify text editor's smart home/end caret positioning preference is followed
- Verify content assist proposal background/foreground color preferences in structured text editor's preference page are followed
- Syntax highlighting preferences:
- Verify content assist works correctly (verify icons in content assist proposals look correct)
- Check Source Editing features from feature feature matrix
- Test Design page, Source page, Outline view, Properties view synchronization
- Test our editors follow preferences in the "All Text Editors" preference page
- Check that editors follow content type specific preferences under Web and XML preference pages
- Make sure editors (already open and closed and reopened) are updated when preferences change
- Check preferences are saved when shutdown and restart workbench
- Web and XML->Content Type Files -> Content Type Source -> Indent using tabs / Indent using spaces -> Indentation size
- Verify the correct tab character is used
- Verify the correct number of tab characters is used
- Verify Source->Shift Left/Shift Right and the Shift-Tab/Tab key follow the preferences
- With nothing selected
- With multiple lines selected
- Verify Format follow the preferences
- Verify when using tab characters, the displayed tab width preference is followed (General->Editors->Text Editors -> Displayed tab width)
- make sure the template creates a valid file
- Verify not entering an extension will generate a new file with the default file extension you specified in the preference.
- Verify entering a file name that already exists without the extension will still give you an error saying the file already exists (for example, if index.jsp already exists, typing "index" will tell you that it already exists)
- Verify entering a file name with valid/invalid extension still works