XML, DTD, XSD Validation M2 test plan
wtp milestone 2 test plan
Status of this Document
 

This is the test plan for the XML, DTD and XSD Validators for the Milestone 2 release. Last updated on 12/14/2004.

Overall goals
Co-developer Testing
 

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.

API Testing
 

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.

UI-Based Functional Testing
 

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.

JUnit Functional Testing
 

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.

Platform Testing
 

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.

Performance Testing
 

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.

Functional Testing
 

JUnit Testing

  • Test to see if a document is valid. The validator should report back correctly that the document is either valid or invalid.
  • Repeat for other documents.
UI-Based Testing
    General Scenario
  • Validate an invalid document and ensure problems are shown as annotations in the editor's source ruler and margin
  • Check that error messages are listed in the problems view
  • Check that navigation works for error markers
  • Check that line numbers match error markers
  • Correct errors and revalidate and ensure all markers and messages are removed
  • Ensure popup message dialog appear with the correct validation message
    XML Catalog
  • Test that validation works with the XML Catalog
    Referenced Files
  • Test errors in referenced files
    • 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
    • Test similarly also for good xml, bad dtd
    Validation Preferences
  • Test validate on file save
  • Turn it on and off
  • Test global vs project settings
  • Test maximum number of messages
  • See test plan for Validation Framework