Test Cases for Data Migration |
|||
|
|
|
|
|
|
|
|
10.DMIGR.TCs01 |
Selection and comparison of three objects |
||
Description |
The user selects three objects and compares them. |
||
Preconditions |
The migration has completed successfully. The initial *.xml file has been transformed into an RFD file of the type *.ttl.xml. The file produced by the migration process is opened in preview mode and the fundamental migrated data are shown on the screen. |
||
Constraints |
Review equivalent files *.xml и *.ttl.xml for the same object. |
||
№ |
Performed action |
Expected result |
Tester notes |
1 |
Select three objects from the *.ttl.xml file at hand. |
The three objects are marked as selected (i.e. : <obj/*******> crm:P****_forms_part_of rkd-collection:Mauritshuis or <obj/*****/1/image> a crm:E38_Image; crm:P***_was_created_by <object******/1/production>>; or <obj/*******/2/production> crm:P****_employed rkd-frame:wood--gold_plated , or any other combination of semantic threesomes of objects from the *.ttl.xml ) |
|
Post conditions |
The three objects are selected |
||
|
|
|
|
|
|
|
|
10.DMIGR.TCs02 |
Comparison of migrated data for object with RDF data (*.ttl.xml) - readable form |
||
Description |
The user searches and finds the equivalent of the preselected threesome of objects to be compared. Validates that the corresponding data in both files is the same. |
||
Preconditions |
The migration has completed successfully. The initial *.xml file has been transformed into an RFD file of the type *.ttl.xml. The two files from the import and export of the migration are opened in preview mode in readable format and the fundamental data are loaded on the screen. The particular threesome that is to be checked is selected. The RDK thesauruses are opened for reference. |
||
Constraints |
Review equivalent files *.xml и *.ttl.xml for the same object. |
||
№ |
Performed action |
Expected result |
Tester notes |
1 |
The user searches for the equivalent of the chosen threesome of RDF data in the *.xml of the object in question. |
The data is found in the *.xml file of the preselected threesome of objects. |
|
2 |
The user compares the fundamental data between the two files. |
The data from the *.xml corresponds to the data of the *.ttl.xml |
|
Post conditions |
The fundamental data is compared and an equivalent is found. |
||
|
|
|
|
|
|
|
|
10.DMIGR.TCs03 |
Comparison of migrated data for object with RDF data (*.ttl.xml) - fail - readable form |
||
Description |
The user searches and finds the equivalent of the preselected threesome of objects to be compared. Validates that the corresponding data in both files is the same. |
||
Preconditions |
The migration has completed successfully. The initial *.xml file has been transformed into an RFD file of the type *.ttl.xml. The two files from the import and export of the migration are opened in preview mode in readable format and the fundamental data are loaded on the screen. The particular threesome that is to be checked is selected. The RDK thesauruses are opened for reference. |
||
Constraints |
Review equivalent files *.xml и *.ttl.xml for the same object. |
||
№ |
Performed action |
Expected result |
Tester notes |
1 |
The user searches for the equivalent of the chosen threesome of RDF data in the *.xml of the object in question. |
The data is found in the *.xml file of the preselected threesome of objects. |
|
2 |
The user compares the fundamental data between the two files. |
The data from the *.xml DOES NOT correspond to the data of the *.ttl.xml |
|
Post conditions |
The fundamental data is compared and an equivalent is NOT found. |
||
|
|
|
|
|
|
|
|
10.DMIGR.TCs04 |
Comparison of migrated data for object with RDF data - visual screen form |
||
Description |
The user searches and finds a visual equivalent of the preselected threesome of objects to be compared and its corresponding data in *xml on the screen. Validates the corresponding data between the *.XML and the RDF, loaded on the screen. |
||
Preconditions |
The migration has completed successfully. The *.xml file of the object in question is validated. In the Owlim are transformed and loaded RDF data on the screen. The particular threesome that is to be checked is selected and its correspondence in the *.xml file. The RDK thesauruses are opened for reference. |
||
Constraints |
Review equivalent files *.xml и RDF data for the same object. |
||
№ |
Performed action |
Expected result |
Tester notes |
1 |
The user searches for the equivalent of the chosen data from the *xml file in the visualized RDF on the screen. |
The data of the preselected entries from the *.xml file is found in the RDF data on the screen |
|
2 |
The user compares the fundamental data. |
The data from the *.xml corresponds to the RDF data on the screen. |
|
Post conditions |
The fundamental data is compared and an equivalent is found. |
||
|
|
|
|
|
|
|
|
10.DMIGR.TCs05 |
Comparison of migrated data for object with RDF data - visual screen form - fail |
||
Description |
The user searches and finds a visual equivalent of the preselected threesome of objects to be compared and its corresponding data in *xml on the screen. Validates the corresponding data between the *.XML and the RDF, loaded on the screen. |
||
Preconditions |
The migration has completed successfully. The *.xml file of the object in question is validated. In the Owlim are transformed and loaded RDF data on the screen. The particular threesome that is to be checked is selected and its correspondence in the *.xml file. The RDK thesauruses are opened for reference. |
||
Constraints |
Review equivalent files *.xml и RDF data for the same object. |
||
№ |
Performed action |
Expected result |
Tester notes |
1 |
The user searches for the equivalent of the chosen data from the *xml file in the visualized RDF on the screen. |
The data of the preselected entries from the *.xml file is found in the RDF data on the screen |
|
2 |
The user compares the fundamental data. |
The data from the *.xml DOES NOT correspond to the RDF data on the screen. |
|
Post conditions |
The fundamental data is compared and an equivalent is NOT found. |