Defining a simple checkpoint with no Integrations
Go to the Checkpoint Studio in the Dodgeball Trust Console
Either choose an existing checkpoint or create a new one
Invoking Checkpoints
Go to the Checkpoint Studio in the Dodgeball Trust Console
Either choose an existing checkpoint or create a new one
A new checkpoint will look like this:
A very simple checkpoint only uses blocks from the “Actions” Tab
Best practices for a simple checkpoint
Use “Decision” Blocks and/or “A/B Test” Blocks to split up workflow traffic
Tools for Invoking Checkpoints
This table summarizes what the available tools are and important information about using those tools:
| Shopify | Bondfire | Demo Examples | Dodgeball Examples | |
|---|---|---|---|---|
| Demo Link | Dev StoreDev Store Config(Points at QA) | Demo Bondfire | QA Dodgeball Demo Examples | Available to run locally via dodgeball-examples on GitHub |
| How to run a checkpoint | Buy something to run “SHOPIFY_CREATE_ORDER” | “LOGIN”“SIGN_UP” &“PURCHASE”Checkpoints are connected | Enter QA API Keys.Configure Checkpoint Name / Event Payload, click “Save Changes” and call the checkpoint. | See README.md |
Features by Tool
This table summarizes what is possible to do with each tool.
Generally, the Demo Examples tool gives a good balance between flexibility and ease of use, but choose the tool on a per-use-case basis based on their individual strengths and weaknesses:
| Feature | Shopify | Bondfire | Demo Examples | Dodgeball Examples |
|---|---|---|---|---|
| Can run any integration? | ❌ | ✅ | ✅ | ✅ |
| Can run any checkpoint? | ❌ | ❌ | ✅ | ✅ |
| Can send any event data? | ❌ | ❌ | ✅ | ✅ |
| Can target integration edge cases? | ❌ | ❌ | ✅ | ✅ |
| Can customize SDKs used? | N/A | ❌ | ❌ | ✅ |
| Can send any server event? | ❌ | ❌ | ❌ | ✅ |
| Can simulate complicated flow for initializing customers/sessions? | ❌ | ❌ | ❌ | ✅ |
| Open Source (customer engineers can reference and experiment with the code) | ❌ | ❌ | ❌ | ✅ |