Test Case Name | Identifier | Category |
Data Model Test | TC-PERSISTENCE-01 | Unit Test |
Description:
To test the validity and integrity of the data model that is based on XPath
data model. The contents of the data model are populated with sample data
values, then the contents are printed out for verification.
The following packages are tested:
Setup:
No particular environment setup is requred other than a JDK and Ant.
Procedures:
Expected Results:
The output is semantically equivalent to the input values.
Requirements:
See the references (in test/persistence), which are extracted from the
XPath 2.0 Data Model.
Related Test Cases:
None
Notes:
Test program is not completed yet (for the printing part).
Issues:
Test Case Name | Identifier | Category |
Data Model Store Test | TC-PERSISTENCE-02 | Unit Test |
Description:
To test if the data model contents are properly stored to the relevant
database tables.
The following packages are tested:
Setup:
The following components are required to run this test.
Procedures:
Expected Results:
The database tables are populated with the input values while keeping
integrities between them.
Requirements:
See the references (in test/persistence), which are extracted from the
XPath 2.0 Data Model.
Related Test Cases:
Notes:
None
Issues:
TBD
Test Case Name | Identifier | Category |
Data Model Load Test | TC-PERSISTENCE-03 | Unit Test |
Description:
To test if the data model contents are properly loaded from the database
tables. A document is loaded by providing its base-uri value.
The following packages are tested:
Setup:
The following components are required to run this test.
Procedures:
Expected Results:
The original document is restored to the model.
Requirements:
Data Model Store Test (TC-PERSISTENCE-02) must have been run successfully
before running this test case. See the references (in test/persistence),
which are extracted from the XPath 2.0 Data Model.
Related Test Cases:
Notes:
None
Issues:
TBD
Test Case Name | Identifier | Category |
XML To Database Test | TC-PERSISTENCE-04 | Unit Test |
Description:
To test if an input XML file is properly stored to the relevant
database tables.
The following packages are tested:
Setup:
The following components are required to run this test.
Procedures:
Expected Results:
The database tables are populated with the contents of the input XML file
keeping proper relational integrities.
Requirements:
See the references (in test/persistence), which are extracted from the
XPath 2.0 Data Model.
Related Test Cases:
Notes:
Data model is built from the input XML file, then is stored to the database
tables.
Issues:
No validation against the XML file is done currently. The validation needs to
be enabled later (before initial release).
Test Case Name | Identifier | Category |
Database To XML Test | TC-PERSISTENCE-05 | Unit Test |
Description:
To test if an XML document is properly restored from the relevant
database tables. This restores the sample XML file (part0001.xml) that has been
added to the database by running XML To Database Test
(TC-PERSISTENCE-04). The XML output is
printed on the screen by default, or can be stored as a file.
The following packages are tested:
Setup:
The following components are required to run this test.
Procedures:
Expected Results:
The XML output is semantically equivalent to the original XML file that was
used in XML To Database Test(TC-PERSISTENCE-04).
Requirements:
See the references (in test/persistence), which are extracted from the
XPath 2.0 Data Model.
Related Test Cases:
Notes:
Alternatively, this test can be run after Data Model Store Test
(TC-PERSISTENCE-04) since this too stores an XML to the database. In this case,
DB2XMLTest.java may need a modification to use the same base URI of
the document for retrieval.
Issues:
No validation against the XML file is done currently. The validation needs to
be enabled later (before initial release).
Test Case Name | Identifier | Category |
Document Remove Test | TC-XMLDB-01 | Subsystem Test |
Description:
To test if an XML document is properly removed from the database. This test
removes the sample XML file (part0001.xml) that has been
added to the database by running XML To Database Test
(TC-PERSISTENCE-04).
The following packages are tested:
Setup:
The following components are required to run this test.
Procedures:
Expected Results:
The sample document "part0001.xml" is deleted from the XML database.
Requirements:
See the references (in test/persistence), which are extracted from the
XPath 2.0 Data Model.
Related Test Cases:
Notes:
This is used for testing the XML:DB implementation.
Issues:
No validation against the XML file is done currently. The validation needs to
be enabled later (before initial release).