| <html><head><META http-equiv="Content-Type" content="text/html; charset=UTF-8"><link type="text/css" href="../../../../..//default_style.css" rel="stylesheet"><link type="text/css" href="../../../../..//webtools/wtp.css" rel="stylesheet"><title>WTP Milestone 5</title></head><body><table border="0" cellpadding="2" cellspacing="5" width="100%"><tbody><tr><td align="left" width="60%"><font class="indextop">CSS Test Plan</font><br><font class="indexsub">WTP Milestone 5</font></td><td width="40%"><img src="../../../../..//webtools/images/wtplogosmall.jpg" align="middle" height="129" hspace="50" width="207" alt="WTP Logo" usemap="logomap"><map id="logomap" name="logomap"><area coords="0,0,207,129" href="/webtools/" alt="WTP Home"></map></td></tr></tbody></table><table border="0" cellpadding="2" cellspacing="5" width="100%"><col width="16"><col width="*"><tbody><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">Status of this Plan</font></b></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><p>Proposed Plan (6.27.05)</p></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">Overall goals</font></b></td></tr><tr><td align="right" valign="top"><img src="../../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td><b>New for M5</b></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><p> |
| Not much has been added in terms of new functionality |
| for M5. Most of the work done was in the areas of |
| refactoring, cleaning up dead code, and cleaning up APIs. |
| Also more unit tests were added which are run regularly |
| with the build. |
| <br><br> |
| The M4 test plan should have sufficient coverage for M5. |
| </p></td></tr><tr><td align="right" valign="top"><img src="../../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td><b>Co-developer Testing</b></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><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></td></tr><tr><td align="right" valign="top"><img src="../../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td><b>API Testing</b></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><p> |
| Here in M5 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. |
| </p></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><p> |
| We do have several hundred unit tests which we expect to be |
| running and passing for M5, which test various |
| aspects of parsing, model creation, and correct charset |
| handling, among other things. |
| </p></td></tr><tr><td align="right" valign="top"><img src="../../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td><b>End User Testing</b></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><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></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><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></td></tr><tr><td align="right" valign="top"><img src="../../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td><b>Platform Testing</b></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><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></td></tr><tr><td align="right" valign="top"><img src="../../../../..//images/Adarrow.gif" border="0" height="16" width="16"></td><td><b>Performance Testing</b></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><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 plugins</b> |
| <br> |
| <br> |
| We will continue to add more test cases in upcoming milestones. |
| </p></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">CSS Tests</font></b></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><ul> |
| <li>check Source Editing features from <a href="../../../../wst/components/sse/M5/milestone_test_plan.html#matrix">feature matrix</a></li> |
| <li> |
| A quick sanity check that preferences have effect, and |
| do no harm. Only quick check, since many changes planned |
| in this are for future milestones. |
| </li> |
| <p> |
| <ul> |
| <li> |
| hyperlink open on: |
| <ul> |
| <li>@import</li> |
| </ul> |
| </li> |
| |
| <li> |
| preferences: |
| <ul> |
| <li>how we use the preferences in the "All Text Editors" |
| preference page now. |
| </li> |
| <li>make sure preferenes work</li> |
| <li>after shutdown and restart</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> |
| </p> |
| </ul></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">New for M5</font></b></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><p> |
| New File Wizard |
| </p></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><ul> |
| <li>make sure the template creates a valid file</li> |
| </ul></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><p> |
| Tab Preferences |
| </p></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><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></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica"><b>Regression Tests</b></font></b></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><p> |
| <a href="../../../../wst/components/sse/M4/formatting-test.html">Formatting tests</a> |
| <br> |
| </p></td></tr><tr><td colspan="2" align="left" bgcolor="#0080c0" valign="top"><b><font color="#ffffff" face="Arial,Helvetica">Source Editing Test Plans</font></b></td></tr><tr><td align="right" valign="top"> |
| |
| </td><td valign="top"><p> |
| <a href="../../../../wst/components/sse/M5/milestone_test_plan.html">org.eclipse.wst.sse</a> |
| <br><a href="../../../../wst/components/xml/M5/milestone_test_plan.html">org.eclipse.wst.xml</a> |
| <br><a href="../../../../wst/components/html/M5/milestone_test_plan.html">org.eclipse.wst.html</a> |
| <br><a href="../../../../wst/components/css/M5/milestone_test_plan.html">org.eclipse.wst.css</a> |
| <br><a href="../../../../wst/components/dtd/M5/milestone_test_plan.html">org.eclipse.wst.dtd</a> |
| <br><a href="../../../../wst/components/javascript/M5/milestone_test_plan.html">org.eclipse.wst.javascript</a> |
| |
| <br><a href="../../../../jst/components/jsp/M5/milestone_test_plan.html">org.eclipse.jst.jsp</a> |
| </p></td></tr></tbody></table></body></html> |
