Testing tools

The testing tools are used to build and test a system solution. You build the components of a system before testing them, and then integrate them into larger components.

These tools perform selected tests by generating appropriate command-line commands along with the correctly ordered requisite parameters.

Use the system tools to perform unit, integration, and system testing on your network configuration.

Testing tools are accessed through the GUI or the command-line.

See each of these Testing tool topics for command-line commands and GUI fields:

  • Database protocol test: This calls the engine command line to test the specified database protocol thread.

    See Testing the database protocol.

  • Database schema test: This parses the database schema format.

    See Testing the database schema.

  • DICOM test: This runs a DICOM ECHO test, by doing a DICOM ping action on the DICOM remote SCP (Service Class Provider). This is to verify the DICOM network between the system DICOM SCU and the remote DICOM SCP.

    See Testing DICOM configurations.

  • JSON test: The JSON data message file is based on the specified JSON schema file. You can select from the current site, master site, and root-level JSON schema files.

    See Testing JSON configurations.

  • LDL test: LDL (Length Delimited Layout) is a data layout used for DICOM. Functionality is similar to FRL and VRL.

    See Testing LDL configurations.

  • Record format test: These tools test configurations by simulating the input-parse portion of the translation engine. These tools read, parse, and display messages, ensuring that configurations match the input data. For example, the FRL tool tests one particular FRL (Fixed Record Layout) for all of its input messages. It then test compiles an FRL to ensure the engine can use it. Using the Testing tool for other record formats is more complex, as other formats encompass entire version or variant sets, which contain many message definitions.
  • Route tests: This simulates most of the translation thread. Given a message, it determines the transaction ID and brings up the appropriate route configuration. This tool outputs messages to a set of files, or to a Tcl end procedure, depending on the end processing configuration.

    See Testing routes.

  • TCP/IP: Use the TCP/IP Test tool to configure, test, and debug TCP/IP connections.

    See TCP/IP.

  • TPS (Tcl Procedure Stream) tests: This simulates most TPS UPoCs (User Points of Control)

    See Testing TPS.

  • Trx ID test: Tests a transaction ID separately from the engine. This simulates getting the transaction ID on an incoming message from the source thread.

    See Testing a transaction ID.

  • Translation tests: After the record format tests verify the input data, use the XLT tool to define a translation specification that converts translation data into another format.

    The only required argument for this test is the name of the translation.

    • If an input file is not supplied, then it checks the translation file for validity.
    • If an input file is supplied, then it internalizes the translation, runs one or more sample input messages through the test.

    For every input message, the translation engine produces an output message. The Translation Configurator parses the input message according to the translation’s input record specification. Then it displays the results according to the chosen detail level. Given an output file name, the XLT tool writes the translated message to that file.

    See Testing XLT configurations.

  • XML test: Built-in support is provided for XML as a message type. XML provides built-in handling of XML messages, in addition to providing support for the recommendations of the W3C (World Wide Web Consortium). The XML tool takes an XML data file and processes it through the parser to determine if it matches the DTD specifications.

    See Testing XML configurations.

  • XSLT: Tests XSLT files.

    See Testing XSLT configurations.

Certain test options are only available with certain modes:

  • Choose Data File and Line Termination Format are available only in run mode.
  • Initial Startup is available in run mode and time mode.
  • Interval and Max Messages are available in time mode.
  • When startup mode or shutdown mode are chosen, only Caller Context and Leak Detection are available.