| <?xml version="1.0" encoding="utf-8"?> |
| <?xml-stylesheet type="text/xsl" href="../../../wtp.xsl"?> |
| <html> |
| <head> |
| <meta name="root" content="../../../../" /> |
| <title>wtp milestone 2 test plan</title> |
| </head> |
| <body> |
| |
| <h1>XML, DTD, XSD Validation M2 test plan</h1> |
| |
| <h2>Status of this Document</h2> |
| <p> |
| This is the test plan for the XML, DTD and XSD Validators for the Milestone 2 release. |
| Last updated on 12/14/2004. |
| </p> |
| |
| <h2>Overall goals</h2> |
| |
| <h3>Co-developer Testing</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>API Testing</h3> |
| <p> |
| Here in M2 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> |
| <h3>UI-Based Functional Testing</h3> |
| <p> |
| For these tests, we want to ensure that the user will be |
| provided with the appropriate feedback of the validation results. |
| This will be via dialogs and tasks that are generated in the |
| problems view. |
| </p> |
| <h3>JUnit Functional Testing</h3> |
| <p> |
| Our primary goal in M2 Functional Testing is to ensure basic |
| functions work. JUnit functional tests will be run for the |
| specified validators to determine if documents are correctly |
| classified as valid or invalid. |
| </p> |
| <h3>Platform Testing</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>Performance Testing</h3> |
| <p> |
| We do not have any specific performance testing planned for |
| M2, but will add automated performance tests along the lines |
| of the Eclipse base performance unit tests in future |
| milestones. |
| </p> |
| |
| |
| <h2>Functional Testing</h2> |
| <p> |
| JUnit Testing |
| <ul> |
| <li>Test to see if a document is valid. The validator should report back correctly that |
| the document is either valid or invalid.</li> |
| <li>Repeat for other documents.</li> |
| </ul> |
| |
| UI-Based Testing |
| <ul><b>General Scenario</b> |
| <li>Validate an invalid document and ensure problems are shown as annotations in |
| the editor's source ruler and margin</li> |
| <li>Check that error messages are listed in the problems view</li> |
| <li>Check that navigation works for error markers</li> |
| <li>Check that line numbers match error markers</li> |
| <li>Correct errors and revalidate and ensure all markers and messages are removed</li> |
| <li>Ensure popup message dialog appear with the correct validation message</li> |
| </ul> |
| <ul><b>XML Catalog</b> |
| <li>Test that validation works with the XML Catalog</li> |
| </ul> |
| <ul><b>Referenced Files</b> |
| <li>Test errors in referenced files</li> |
| <ul> |
| <li>good xml, bad xsd. ie. XSD errors should not show in XML resource. There should be |
| however one message to indicate that there are errors in the referenced file</li> |
| <li>Test similarly also for good xml, bad dtd</li> |
| </ul> |
| </ul> |
| <ul><b>Validation Preferences</b> |
| <li>Test validate on file save</li> |
| <li>Turn it on and off</li> |
| <li>Test global vs project settings</li> |
| <li>Test maximum number of messages</li> |
| <li>See test plan for Validation Framework</li> |
| </ul> |
| |
| </p> |
| |
| </body> |
| </html> |
| |
