export process under R101.4.19. This should be noted by the test centre in the test observations. Export the C The initial export from 5.3 should be compared against the final export from 5.2 disposal holding Test Script Disposal Session Day One – – service under The exported data has its own universally unique export identifier, R11.4.1 (including under R11.4.4 residual entities The exported data has the text comment, case T5.3.3C: initial “Test under R11.4.2) export of disposal holding service” under R11.4.5 The exported data matches that expected under R11.4.3, R11.4.6, The text comment R11.4.7 and R11.4.9 for the export Definitive comparative test data is not yet available, as the test framework under R11.4.5 is in beta, and export data must currently be checked by hand should be: “Test The export identifier and export comment can be found in the export case T5.3.3C: event generated under R11.4.10, and stored in the event history of initial export of each entity exported disposal holding The exported XML data is in Unicode, under R2.4.28 service” All textual metadata elements in the exported XML data are accompanied by a language identifier, under R2.4.28
export process under R101.4.19. This should be noted by the test centre in the test observations. C Export the disposal holding 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.3.3C: initial export of disposal holding service” The initial export from 5.3 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.3.3C: initial export of disposal holding 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 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
MoReq2010-Test-Module-5-Disposal.docx