This is the test plan for the XML Catalog for the Milestone 2 release. Last updated on 12/15/2004.

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 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.

Our primary goal in M2 End-User Testing is to ensure basic functions work. Specifically, we want to confirm that the user is able to add, modify and delete catalog entries.

I might also point out that 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 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.

• Add an XML Catalog entry with the following properties, for an XML document




Test	Key	Key Type	URI
1.	web (http) reference to file	Public ID	any workspace file
2.	web (http) reference to file	System ID	any workspace file
3.	Workspace file	Public ID	any workspace file
4.	Workspace file	System ID	any workspace file

• Add an XML Catalog entry with the following properties, for an XML Schema document




Test	Key	Key Type	URI
1.	web (http) reference to file	Schema Location	any workspace file
2.	web (http) reference to file	Schema Location	any workspace file
3.	Workspace file	Namespace Name	any workspace file
4.	Workspace file	Namespace Name	any workspace file

You can keep these entries when you test the tools or editors that make use of the catalog.

• Edit an entry
• Delete an entry
• Export an XML Catalog setting to the filesystem
• Import an XML Catalog setting from the filesystem