B Export the disposal The initial export should be compared against the final export from scheduling service 5.2 Test Script Disposal Session Day One – – under R11.4.1 The exported data has its own universally unique export (including residual identifier, under R11.4.4 entities under The exported data has the text comment, case T5.4.8B: “Test R11.4.2) initial export of disposal scheduling service” under R11.4.5 The text comment The exported data matches that expected under R11.4.3, R11.4.6, for the export under R11.4.7 and R11.4.9 R11.4.5 should be: Note: Definitive comparative test data is not yet available, as the case T5.4.8B: “Test test framework is in beta, and export data must currently be initial export of checked by hand disposal scheduling The export identifier and export comment can be found in the service” export event generated under R11.4.10, and stored in the event history of each entity exported The exported XML data is in Unicode, under R2.4.28 All textual metadata elements in the exported XML data are accompanied by a language identifier, under R2.4.28 All timestamps in the exported XML data are in the W3C XML dateTimeStamp format and include time zone information, under R2.4.27
B Export the disposal scheduling service under R11.4.1 (including residual entities under R11.4.2) The text comment for the export under R11.4.5 should be: “Test case T5.4.8B: initial export of disposal scheduling service” The initial export should be compared against the final export from 5.2 Test Script – Disposal – Session Day One The exported data has its own universally unique export identifier, under R11.4.4 The exported data has the text comment, “Test case T5.4.8B: initial export of disposal scheduling service” under R11.4.5 The exported data matches that expected under R11.4.3, R11.4.6, R11.4.7 and R11.4.9 Note: Definitive comparative test data is not yet available, as the test framework is in beta, and export data must currently be checked by hand The export identifier and export comment can be found in the export event generated under R11.4.10, and stored in the event history of each entity exported The exported XML data is in Unicode, under R2.4.28 All textual metadata elements in the exported XML data are accompanied by a language identifier, under R2.4.28 All timestamps in the exported XML data are in the W3C XML dateTimeStamp format and include time zone information, under R2.4.27
MoReq2010-Test-Module-5-Disposal.docx