Testing XML configurations

Parses an XML test message against a DTD/Schema/DTD-containing-XML file. The test process validates the consistency of the message and DTD/Schema/DTD-containing-XML.

You can also explicitly name the message definition to test.

Before running the XML test, place on the server a compatible pair of files consisting of a test XML message and a DTD/Schema/DTD-containing-XML file.

A pre-test is required on the DTD/Schema/DTD-containing-XML file. This pre-test is performed through the Compile option on the XML Package Manager.

After the pre-test is finished, take note of the package containing the pre-tested DTD/Schema/DTD-containing-XML file. This pre-tested file must be referenced within the XML test message that is used in the Testing Tool validation and test parse.

  1. For Package, click the arrow to open a list of available packages on the server machine (HCIROOT\HCISITE\formats\xml\). Select the package containing the prepared DTD/Schema/DTD-containing-XML file.
  2. For XML, select the message definition from the list.
  3. Specify the testing data file in Choose Data File. You can also click the folder button to open a file browser to select the data file. By default, the file browser locates on the $HCISITEDIR/formats/ folder.
  4. Open the Detail level menu to select from a list of detail levels for the test output that is reported in the Result pane. Detail levels go from 0 (raw, unparsed data) to 4 (most detail).
  5. Select the line termination format in which to save the test messages. Click the arrow to open a list of formats.
    Newline Terminated reads the data in the file until it finds a newline character, making all that data one message, and sends that to the parser. It then reads until it finds the next newline character, makes a second message, and sends that to the parser.
    Length Encoded reads the first 10 characters to determine the first message length. Then it reads that many characters into a message, and sends it to the parser.
    EOF Terminated reads the file until it gets to the end-of-file character, takes that as a message, and sends it to the parser.
  6. Specify the encoding in the Encoding field. You can also click the arrow to open a list of different encodings that identify the encoding of messages in the selected data file. The command converts the messages from the identified encoding to UTF-8 to perform the test. When you select an encoding from the list, an -e encoding option is added to the corresponding command line.
  7. Select how to process records.
    process all records reads the selected data file and processes all the records in it.
    process one record reads the selected data file and processes only the first record in the file.
  8. Select Print unreadable chars without changing to hex to print the output in pretty print.
  9. If required, then select Grep to filter the output.
  10. Click Run Command to run the command shown in Preview Command to Issue.
    As the test is being configured, a command-line command and the requisite parameters are generated in Preview Command to Issue. This is for display only. A command cannot be manually entered.