ProcessMIX Guide
  • Platform Overview
    • Introduction
    • Platform Purpose
    • Main Concepts
      • Organization Structure
      • Visual Language
      • Project Development Environment (IDE)
      • Deployment and Integration
      • Administration and Troubleshooting
    • First Steps
    • Change Log
      • 5.0.0
      • 5.0.5
      • 5.0.5.1
      • 5.0.5.2
      • 5.0.5.3
      • 5.0.5.4
  • Language Reference Guide
    • Overview
    • Data Structures and Types
      • Core Types (pdk.core)
      • Dictionary (pdk.asset.dictionary)
      • Scorecard (pdk.asset.scorecard)
      • Blockchain (pdk.blockchain)
      • Exceptions (pdk.ex)
      • Input/Output (pdk.io)
      • JSON Web Token (pdk.jwt)
      • Networking (pdk.net)
      • HTTP (pdk.net.http)
      • SOAP/Web Services (pdk.net.soap)
      • XML/DOM (pdk.net.xml)
      • S3 (pdk.s3)
      • SQL (pdk.sql)
      • Postgres (pdk.db.postgre)
      • Util (pdk.util)
      • Default Data Structure Field Values
    • Flows
      • Variables
        • Local Flow Variables
        • Node Variables
      • Flow Node Types
        • Core Nodes
          • In
          • Out
          • Assign
          • If
          • Switch
          • Iterator
          • Function Call
          • Subflow
          • Raise Exception
          • Exception Handler
          • Validator
        • Connector Nodes
          • Database Begin Transaction
          • Database Commit Transaction
          • Database Rollback Transaction
          • Database Query Executor
          • EVM Blockchain Functions
          • EVM Blockchain Smart Contract Functions
          • REST Service Executor
          • SOAP Service Executor
          • S3 Connector
          • SMB Connector
      • Expressions
      • Built-In Functions
        • Expression functions
          • pdk.util.Any
          • pdk.util.Array
          • pdk.util.Blockchain
          • pdk.util.Cast
          • pdk.util.Codec
          • pdk.util.Crypto
          • pdk.util.Date
          • pdk.util.File
          • pdk.util.Json
          • pdk.util.JWT
          • pdk.util.Map
          • pdk.util.Math
          • pdk.util.String
          • pdk.util.Util
        • Node functions
          • pdk.flow.Any
          • pdk.flow.Array
          • pdk.flow.File
          • pdk.flow.JsonArray
          • pdk.flow.JsonObject
          • pdk.flow.HttpRequest
          • pdk.flow.HttpResponse
          • pdk.flow.Logger
          • pdk.flow.Map
          • pdk.flow.Xml
            • pdk.flow.xml.XmlAttr
            • pdk.flow.xml.XmlElement
            • pdk.flow.xml.XmlNode
            • pdk.flow.xml.XmlDocument
            • pdk.flow.xml.XmlDocumentType
            • pdk.flow.xml.XmlDOMConfiguration
            • pdk.flow.xml.XmlDOMImplementation
            • pdk.flow.xml.XmlProcessingInstruction
            • pdk.flow.xml.XmlTypeInfo
            • pdk.flow.xml.XmlCharacterData
            • pdk.flow.xml.XmlText
            • pdk.flow.xml.XmlNamedNodeMap
          • pdk.node.BlockchainEth
          • pdk.node.S3
          • pdk.node.Smb
      • Exceptions
        • Checked Exceptions
        • Runtime Exceptions
    • Assets
      • Dictionary
      • Decision Table
      • Scorecard
      • PMML
    • Connectors
      • DB Connector
        • Prepared Query
        • Dynamic Query
        • Query input parameters
        • Stored Procedure
      • REST Connector
      • SOAP Connector
      • S3 Connector
      • SMB Connector
      • EVM Blockchain Connector
    • Global Variables
    • Appendices
      • Overview of Database Transactions
      • Reserved Words
  • Project Development Environment (IDE)
    • Project Explorer Panel
    • Flow Builder
    • Flow Node Editor
    • Data Structure Builder
    • Connector Builders
      • REST Connector Builder
      • SOAP Connector Builder
      • DB (Database) Connector Builder
      • EVM Blockchain Connectors Builder
      • S3 Connector Builder
    • Asset Builders
      • Dictionary Builder
      • Decision Table Builder
      • Scorecard Builder
      • PMML Asset Builder
    • Global Variables Panel
    • Expression Editor
    • Project Deployment and Execution
    • Cron Expression Generator
    • Test Helper
    • Debugging the Project
    • DB transactions
    • Team Collaboration Tools
      • Version Control
      • Conflict Resolver
    • Selectors
    • Error Panel
    • Local History
  • Home and Administration Guide
    • Organization and Subscription
    • Organization Team
    • Repositories and Projects
    • Environments
    • Deployments
    • Database Provisioning
    • Roles and Permissions
  • Logs and Troubleshooting
    • Request/Call Logs
    • Deployment Logs
    • Application Logs
  • Appendix: Example Project
    • Risk Mitigation Solution
Powered by GitBook
On this page
  1. Project Development Environment (IDE)

Test Helper

PreviousCron Expression GeneratorNextDebugging the Project

Last updated 7 months ago

The Test helper is a tool designed to test whether a flow's output is as expected. In other words, you can set the values of the flow's input parameters and check the output.

How To Use the Test Helper?

The Test helper becomes available only after all compilation errors are fixed and your project is deployed. To start testing, click the Test helper pop-up call button.

The Test helper pop-up window will open, and all the flows of a deployed project will be displayed on the left.

Select the required flow, fill in the request data structure in the “Requests” section, then click the RUN button. After execution you will see the response body in the "Response" section and will be able to decide whether the flow has run as expected.

You can use the Download sample button to generate an example of a request that can be used to format or structure a request correctly. Adjust values if necessary.

For REST flows, the Download sample icon is available only for complex data structures containing elements of different types. For SOAP flows and for subflows the button is always available.

When testing requests for all REST flow methods, the Headers are additionally specified. They contain information about the request, such as data format, language, content type, and other settings. The Headers that were generated automatically cannot be modified, for example:

  • Content-Type: application/json. The application sends the request content as data in JSON format.

  • Accept: application/json. The application is waiting for a response in JSON format.

You can edit and delete headers you have created using the context menu options.

To save the test for future reuse, click the SAVE button. In the opened pop-up, enter a name and a description of the test, and click the CREATE button. A saved test will be displayed on the left side of the pop-up in the “Save tests” tab.

The last 10 unsaved tests are displayed on the left side of the pop up in the “Last 10 not saved tests” tab.

As a part of test helper, there is an available option in the flow settings Initialize variables. If initialized variables are activated then output and local variables are initialized with default values according to the data types. Otherwise, the default value is NULL.

In case of any issues, use the debugging mode to check values in the specific nodes in the flow.

How To Prepare an XML (SOAP) Request?

If your flow uses the SOAP channel type, you can use a test helper to test XML requests.

  1. Go to the Test helper pop-up, select the required flow, and click the "Download request" to view the request structure.

  2. Wrap your XML data in tags and click the RUN button. If the request is correct, you will receive a response

For example, if the input data consists of your custom data structure.

You can add a new header to the existing ones by clicking the Add icon. An additional line will appear in the headers where you specify its name and value.