Run a suite on Connect

Diteko runs tests with Connect’s own native testing: Connect simulates each call against the deployed flow, so nothing dials a phone number.

Before you start:

• The server is connected to Amazon Connect.
• The project is linked to its flow on Connect: imported from Connect, or given its Connect flow ID on the Flow stage.
• For a live run, your key has the PUBLISH_LIVE scope.

Dry run first

On the Run stage, set Run mode to Dry run. Every test is converted to Connect’s format and checked, and the results read Checked, not run. Anything that cannot be expressed on Connect (a value a test cannot set, for example) is reported here, before anything is billed.

Live run

Set Run mode to Live on Connect. Diteko creates the test cases in Connect, named after the server and run so they never collide with another team’s, runs at most five at a time, backs off when Connect throttles, and fills in a verdict for each test as it lands. Live executions are billed by Amazon.

From Python:

# Waits for the verdicts; wait=False returns at once
execution = suite.publish_to_connect(dry_run=False)
print(execution.passed, execution.failed, execution.inconclusive)

Every execution stays in Results, across all projects.

Clearing up

Test cases Diteko created stay in Connect, so running a suite again updates them instead of duplicating them. Settings › Remove published test cases deletes the ones this server made, and only those.