| <?xml version="1.0" encoding="utf-8"?> |
| <?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?> |
| <html> |
| <head> |
| <meta name="root" content="../../../www/" /> |
| <title>jsp wtp 2.0 final test plan</title> |
| </head> |
| <body> |
| <h1>jsp wtp 2.0 final test plan</h1> |
| <h2>Status of this Plan</h2> |
| <p>Proposed Plan (5.14.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> |
| JSP API unit tests are in the org.eclipse.jst.jsp.core.tests |
| and org.eclipse.jst.jsp.ui.tests plugins, located in the |
| <i>tests</i> |
| folder in the jst.jsp component. |
| </p> |
| <p> |
| 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. |
| </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> |
| |
| <p> |
| 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 |
| <i>testdata</i> |
| directory under the |
| <i>development</i> |
| directory of relevant component so that testers (from |
| immediate team, or community) can easily check out into the |
| environment being tested. |
| </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 currently in the |
| <b>org.eclipse.wst.*.ui.tests.performance</b> |
| and |
| <b>org.eclipse.jst.jsp.ui.tests.performance</b> |
| plugins. |
| <br /> |
| <br /> |
| We will continue to add more test cases in upcoming |
| milestones. |
| </p> |
| <h2>Testing focus for 2.0</h2> |
| <ul> |
| <li> |
| Run updated |
| <a |
| href="../../../../jst/components/jsp/tests/taglib-test.html"> |
| jsp taglib regression test |
| </a> |
| (updated for jsp 2.0 support) |
| </li> |
| <li>Verify quick fix for spelling mistakes works</li> |
| <li> |
| Formatting: |
| <ul> |
| <li> |
| Verify format with no selection will format |
| document while format while text selected will |
| only format selected text |
| </li> |
| <li> |
| Verify whitespace is preserved between jsp |
| scripts and text/other tags |
| </li> |
| <li> |
| Make sure to run |
| <a |
| href="../../../../wst/components/sse/tests/formatting-test.html"> |
| formatting regression test |
| </a> |
| </li> |
| </ul> |
| </li> |
| <li> |
| Preferences: |
| <ul> |
| <li> |
| Syntax highlighting preferences: |
| <ul> |
| <li> |
| Verify font styles (bold, italics, |
| strikethrough, etc) are obeyed |
| </li> |
| <li> |
| Verify background syntax color |
| preference is followed (especially jsp |
| syntax elements preference) |
| </li> |
| </ul> |
| </li> |
| <li>Verify keywords for preference pages works</li> |
| <li> |
| Verify text editor's smart home/end caret |
| positioning preference is followed |
| </li> |
| <li> |
| Verify hyperlinking preferences in text editor's |
| hyperlinking preference page is followed |
| </li> |
| <li> |
| Verify content assist proposal |
| background/foreground color preferences in |
| structured text editor's preference page are |
| followed |
| </li> |
| </ul> |
| </li> |
| <li> |
| Verify tree path of current selection is displayed in |
| status line |
| </li> |
| <li> |
| Verify attribute hint (shift+ctrl+space) works and bolds |
| existing attributes |
| </li> |
| <li> |
| Verify JSP Fragment, Web Content Settings, and Task Tags |
| preference/properties pages are correct and correctly |
| followed for workspace vs project vs file. |
| </li> |
| <li> |
| Make sure to run |
| <a |
| href="../../../../wst/components/sse/tests/action-test.html"> |
| structured text editor action regression test |
| </a> |
| </li> |
| </ul> |
| <h2>JSP Tests</h2> |
| <ul> |
| <li> |
| Check Source Editing features from |
| <a href="../../wst/sse/test_plan.php#matrix"> |
| feature matrix |
| </a> |
| </li> |
| <li> |
| Check "embedded languages" (Java, HTML, CSS, |
| JavaScript) have same features as indicated in matrix |
| </li> |
| <li> |
| Test standard samples |
| <ul> |
| <li>In HTML "text/html" content type</li> |
| <li>In XHTML "text/html" content type</li> |
| <li>In XHTML "text/xml" content type</li> |
| <li>All in JSP syntax and XML syntax</li> |
| </ul> |
| </li> |
| <li> |
| Test files with different doctype declarations and |
| output types (via page directive) |
| <ul> |
| <li>Test HTML, XHTML, XML</li> |
| <li>Test all files created from templates</li> |
| </ul> |
| </li> |
| <li> |
| Test debug breakpoints can be set/unset, displayed in |
| left-hand-ruler, breakpoint view (see |
| <a |
| href="../../../../jst/components/jsp/tests/jsp-breakpoint-test.html"> |
| JSP Breakpoint tests |
| </a> |
| ) |
| </li> |
| <li> |
| Quick test that breakpoints do indeed 'break' (we'll use |
| Tomcat) |
| </li> |
| <li> |
| As you type validation: |
| <ul> |
| <li> |
| Job based, make sure squiggles show up when they |
| should and are removed when problems are fixed |
| </li> |
| <li> |
| Test various partition types in the document |
| (JSP, HTML, EL) |
| </li> |
| |
| </ul> |
| </li> |
| <li>JSP validation (batch validator)</li> |
| <ul> |
| <li>Make sure prolems show up in problems view</li> |
| <li>Error icons should "gray" out when fixed</li> |
| </ul> |
| <li> |
| HTML validation: |
| <ul> |
| <li>Batch workbench validation, as-you-type</li> |
| </ul> |
| </li> |
| |
| <li>EL support</li> |
| <ul> |
| <li>Vvalidation (batch, as-you-type)</li> |
| <li>Content assist</li> |
| </ul> |
| <li>Background syntax highlighting for JSP regions</li> |
| <ul> |
| <li>Configure via JSP Styles page</li> |
| </ul> |
| <li> |
| Hyperlink open on: |
| <ul> |
| <li> |
| Java Elements, href, includes, link, style, |
| etc... |
| </li> |
| </ul> |
| </li> |
| <li> |
| Test Source page, Outline view, Properties view |
| synchronization |
| </li> |
| <li> |
| Preferences: |
| <ul> |
| <li> |
| Test our editors follow preferences in the "All |
| Text Editors" preference page |
| </li> |
| <li> |
| Check that editors follow content type specific |
| preferences under Web and XML preference pages |
| </li> |
| <li> |
| Make sure editors (already open and closed and |
| reopened) are updated when preferences change |
| </li> |
| <li> |
| Check preferences are saved when shutdown and |
| restart workbench |
| </li> |
| </ul> |
| </li> |
| |
| <li> |
| Tab Preferences: |
| <ul> |
| <li> |
| Web and XML->Content Type Files -> Content Type |
| Source -> Indent using tabs / Indent using |
| spaces -> Indentation size |
| </li> |
| |
| <li>Verify the correct tab character is used</li> |
| <li> |
| Verify the correct number of tab characters is |
| used |
| </li> |
| <li> |
| Verify Source->Shift Left/Shift Right and the |
| Shift-Tab/Tab key follow the preferences |
| </li> |
| <li>With nothing selected</li> |
| <li>With multiple lines selected</li> |
| <li>Verify Format follow the preferences</li> |
| <li> |
| Verify when using tab characters, the displayed |
| tab width preference is followed |
| (General->Editors->Text Editors -> Displayed tab |
| width) |
| </li> |
| </ul> |
| </li> |
| <li> |
| New File Wizard: |
| <ul> |
| <li>make sure the template creates a valid file</li> |
| <li> |
| Verify not entering an extension will generate a |
| new file with the default file extension you |
| specified in the preference. |
| </li> |
| <li> |
| 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) |
| </li> |
| <li> |
| Verify entering a file name with valid/invalid |
| extension still works |
| </li> |
| </ul> |
| </li> |
| <li> |
| General Content Settings |
| <ul> |
| <li> |
| Verify project properties are inherited when |
| file properties are not set |
| </li> |
| <li> |
| Verify setting properties actually saves the |
| properties settings when you reopen properties |
| dialog and when you restart workbench |
| </li> |
| <li> |
| Verify properties still valid/saved when you |
| move the associated file |
| </li> |
| <li> |
| Verify nothing funny happens with build or if |
| you have a readonly project or something that |
| nothing goes wrong (since properties are stored |
| inside project) |
| </li> |
| </ul> |
| </li> |
| <li> |
| JSP Fragment |
| <ul> |
| <li> |
| Verify JSP Fragment shows up in Properties |
| dialog for jsp fragment files and web projects |
| (and only then) |
| </li> |
| <li> |
| Verify Language/Content Type/Validation |
| properties are used when not specified in JSP |
| Fragments |
| </li> |
| </ul> |
| </li> |
| <li> |
| Web Content Settings |
| <ul> |
| <li> |
| Verify Web Content Settings shows up in |
| Properties dialog for html, jsp, css files and |
| web projects (and only then) |
| </li> |
| <li> |
| For CSS files, there should only be a CSS |
| Profile option. Verify it is used For HTML/JSP |
| files there should also be a Document type |
| option. |
| </li> |
| <li> |
| Verify it is used (for example, specify frameset |
| doctype and verify content assist proposes |
| frameset tag) |
| </li> |
| </ul> |
| </li> |
| <li> |
| Profiling: |
| <ul> |
| <li> |
| Using your favorite profiler ( |
| <a |
| href="http://eclipsefaq.org/chris/xray/index.html"> |
| XRay |
| </a> |
| , YourKit, etc...) test basic editor functions |
| and look for problem areas (large memory |
| consumption, intense CPU usage) |
| </li> |
| </ul> |
| </li> |
| </ul> |
| <h2> |
| <b>Regression Tests</b> |
| </h2> |
| <p> |
| <a |
| href="../../../../jst/components/jsp/tests/jsp-breakpoint-test.html"> |
| JSP Breakpoint tests |
| </a> |
| <br /> |
| <a |
| href="../../../../jst/components/jsp/tests/taglib-test.html"> |
| JSP Taglib tests |
| </a> |
| <br /> |
| <a |
| href="../../../../wst/components/sse/tests/viewerconfig-test.html"> |
| Structured Text Viewer Configuration tests |
| </a> |
| <br /> |
| <a |
| href="../../../../wst/components/sse/tests/action-test.html"> |
| Structured Text Editor Action tests |
| </a> |
| <br /> |
| <a |
| href="../../../../wst/components/sse/tests/formatting-test.html"> |
| Formatting tests |
| </a> |
| <br /> |
| <a |
| href="../../../../wst/components/sse/tests/codefolding-test.html"> |
| Code Folding tests |
| </a> |
| <br /> |
| </p> |
| |
| <h2>Source Editing Test Plans</h2> |
| <p> |
| <a href="../../wst/sse/test_plan.php"> |
| org.eclipse.wst.sse |
| </a> |
| <br /> |
| <a href="../../wst/xml/test_plan.php"> |
| org.eclipse.wst.xml |
| </a> |
| <br /> |
| <a href="../../wst/html/test_plan.php"> |
| org.eclipse.wst.html |
| </a> |
| <br /> |
| <a href="../../wst/test_plan.php">org.eclipse.wst.css</a> |
| <br /> |
| <a href="../../wst/dtd/test_plan.php"> |
| org.eclipse.wst.dtd |
| </a> |
| <br /> |
| <a href="../../wst/javascript/test_plan.php"> |
| org.eclipse.wst.javascript |
| </a> |
| <br /> |
| <a href="../jst/jsp/test_plan.php">org.eclipse.jst.jsp</a> |
| </p> |
| </body> |
| </html> |
