# Testing Nodes

# Node: HTTP Testcase

This node is entry point for your test case if the flow you are going to test is an API. HTTP Testcase node can only invoke the EventListener node which is having API gateway as the Event Source. The node supports the features that a typical REST client like POSTMAN supports.

# Properties

  • Method - HTTP method associated with your API configured in your EventListener node.
  • Path - Path of your HTTP endpoint configured in your EventListener node.
  • Headers - Headers that you would like to send as part of your HTTP call.
  • Auth - Supports BasicAuth and Bearer token. This is applicable if your API endpoint is protected by any one of the security model.
  • Body- Body or HTTP payload that you need to pass.

# Node: TestCase

TIP

It is expected that when you use this node you must be aware of AWS events. For example following is the event structure of SQS - SQS Event Details (opens new window)

TestCase represents the entry point for your test case if you intend to test the flows which are primarily non-API based. TestCase node is an advanced node which gives flexibility to modify the events associated with the EventSource configured in your EventListener node.

# Properties

  • TargetNode - Specify the target node that will receive the test payload. The target node must be deployed on the main tab.

  • Payload - Specify the payload to be sent to the target node. Please note that the designer will assist you by providing an example payload depending on the type of the target node. So for example, if the target node accepts S3 events, this payload will be pre-populated with an example of valid AWS Event payload for S3.

# Node: TestCaseEnd

TestCaseEnd node represents the termination of the testcase. Every single flow (main or test) in Kumologica requires a termination node.

# Node: Assertion

Assertion node will receive the response from the main flow (starting from the targetNode). This node is responsible to assert the response received.

# Properties

  • Selector - Indicates what part of the response is to be asserted. Possible values: StatusCode, Headers, JSON Body or Text body.
  • Property - Indicates what property to be assert. Applicable only to Headers and JSON Body.
  • Comparison - Comparison to be computed between the property and the expected value.
  • Type - Expected type if the asserted value, one of string, number, boolean, default string.
  • Value - Expected value in the assertion.

← Overview →