Flurry

How Flurry Works

Define Tasks

Create dispatcher and listener tasks that connect to your system's integration points.

Define Assertions

Add assertions to validate responses and events. Write custom JavaScript functions for advanced validation.

Define Flows

Arrange tasks into flows that model your system's event and command sequences.

Run & Monitor

Run flows in a collection via the Flurry CLI.

Highlights of current and upcoming features

Building Blocks

Dispatcher Tasks

HTTP Requests

AWS SQS messages

AWS Kinesis events

Apache Kafka messages

Listener Tasks

Webhooks

AWS Kinesis events

Apache Kafka messages

Take Action

Comparison, length and existence assertions

Set variables from payload values

Custom JavaScript functions for complex assertions and variable management

Encode and decode Apache Avro data

Encode and decode Protobuf data

AWS Glue Schema registry integration for Apache Avro, Protobuf and JSON schemas

Orchestration

Single or parallel task execution in flows

Extend base assertions with flow specific assertions

Enable/disable flows on a per environment basis

Execution

Run the CLI anywhere with a simple npx command

Define and use environment specific variables

Get variables from process.env within the CLI's running environment

Load testing through parallel collection runs

Performance metrics

Security first

Flurry is built with security in mind. Sensitive data like API keys and AWS credentials stay with you. Simply configure these in your local environment where you run the Flurry CLI. Features that send data into our system, like collection run metrics, are optional. You decide what features to opt into.

Testing event-driven systems, simply.