Skip to content
Rival Docs

Testing Your Tool

You can test your tool directly in the browser before publishing any version. Testing happens in Step 2 (Code & Test) of the tool editor.

How testing works

  1. Write your code in the editor
  2. Open the Test panel
  3. Enter a JSON object as your event input
  4. Click Run
  5. The result appears in the output panel

Your code is executed live against the real execution engine — the same environment your users will get.

The event input

The test event is a JSON object that becomes the event parameter in your handler. For example:

{
    "num": [10, 20, 30, 40, 50]
}

Then in your Python handler:

def cortexone_handler(event, context):
    numbers = event["num"]
    total = sum(numbers)
    return {"statusCode": 200, "body": {"total": total}}

Saving test events

You can save a test event by giving it a name. Saved events are stored on the version and can be re-used across sessions. This is useful for keeping a library of test cases — happy paths, edge cases, error inputs.

Testing Storm tools

Storm tools have a different test interface:

  1. Choose input type:
    • Text — enter a JSON payload directly in the editor
    • Data Source — select a digital asset (uploaded file) as input
  2. Choose output type:
    • JSON — results returned inline in the output panel
    • Data Outbound — results written to a target digital asset you select
  3. Click Run

See the Storm guide for details on the event format.

Execution environment during testing

Errors

If your handler throws an error or times out, the output panel shows the error message and any logs produced before the failure.