This feature is used to do remote testing of the operation and flow of UDTT visually. Some special parameters are mandatory, such as dse_sessionId, dse_applicationId, dse_pageId, etc. They have been packaged into this feature.
Markdown documents can be obtained through the UDTT API Document function. This provides real-time online testing tools in conjunction with API documentation and debugging, against API documentation. Users who did not use UDTT Tooling design process can use the online test tool to display the runtime data model, facilitating debugging. You can also draw Flow charts from XML Flow files.
The test tool can be downloaded from the UDTT build and deployed to any Web container.
Restrictions and constraints
The remote project must be in DEV_MODE mode for the test tool to work. It is defined in web.xml file. The default value is ‘false’ and must be changed to ‘true’.
Remote testing for operation and flow
▪ First, configure the remote IP, port and content. They can be found in markdown file or by oral.
▪ Flow tests must be performed within a session. A session is managed in session management page.
▪ Operation test without a session.
▪ Operation and Flow display interface.
These are processed by runtime XML and not by the transaction file. So the flow chart can be shown even though it is an old project which does not have a transaction file.
Analyze and provide formatted JSON data presentation for operation/flow from runtime XML
Analyze other information (id, type, context, and so on)
▪ ‘Validation page’ helps to assess the validity of a JSON format. Click ‘Validate’ to perform a validation on the displayed JSON content.
