Test suites

name: Invoice goes past due, then is paid
given:
  baseline: clean                # suite snapshot restored first
  history:                       # written with timestamps in the past
    - action: update
      target: { collection: invoices, ids: [in_1042] }
      params: { set: { status: open, due_date: "{{date-3d}}" } }
      ago: 10d
when:
  - at: +0m
    action: transition
    target: { collection: invoices, ids: [in_1042] }
    params: { to: past_due }
    as: overdue
  - at: +1m
    action: wait                 # hold until your system reads it
    target: { ref: overdue }
    params: { for: read, timeout: +15m }
  - at: +5m
    actor: finance@northwind.example
    action: update
    target: { ref: overdue }
    params: { set: { status: paid, amount_paid: 1200 } }
then:
  - kind: call                   # your system called the API
    by: +10m
    method: GET
    path: /v1/invoices/in_1042
  - kind: call
    by: +20m
    method: POST
    path: /v1/invoices/*/send
    none: true                   # ...and never sent a reminder
  - kind: state                  # data your system wrote back
    by: +20m
    target: { collection: notes, where: [{ field: invoice, op: eq, value: in_1042 }] }
    count: { min: 1 }
  - kind: observed               # only your product can show this
    by: +15m
    expect: The customer's account shows as up to date
options:
  speed: 60                      # an hour of timeline a minute

curl -X POST https://api.slurry.io/v1/suites/billing/draft -H "Authorization: Bearer $SLURRY_ACCOUNT_KEY" -H "Content-Type: application/json" -d '{
  "prompt": "An open invoice goes past due, the customer pays half a day later and disputes the rest. Our system should fetch each change within five minutes and never send a second reminder after the payment."
}'

# 200: draft cases (not saved), what Slurry understood, and its questions
{ "cases": [ { "name": "...", "definition": { "given": {}, "when": [], "then": [] }, "validation": { "ok": true, "errors": [], "warnings": [] } } ],
  "playback": [ "1. Invoice in_1042 is open and due in three days", "2. At +0m it moves to past_due", "..." ],
  "questions": [] }

# refine: send the draft back with your answer
curl -X POST https://api.slurry.io/v1/suites/billing/draft -H "Authorization: Bearer $SLURRY_ACCOUNT_KEY" -H "Content-Type: application/json" -d '{ "prompt": "...", "previous": { ... }, "answer": "The reminder is POST /v1/invoices/{id}/send" }'

{
  "at": "+0m", "action": "teams.meeting", "actor": "priya.shah@acme.example", "as": "steerco",
  "params": {
    "subject": "Claims Modernisation steering committee",
    "attendees": "tom.evans@acme.example, Sam Taylor, dana.whitlock@vendorco.example",
    "declined": "Sam Taylor",
    "start": "-2h", "minutes": 60,
    "lines": "Priya Shah: Apologies from Sam again, so we cannot approve the change request today.\nTom Evans: I am on leave from the 3rd for four weeks. Dana covers the cutover plan.\nPriya Shah: Decision recorded: the dress rehearsal moves to 14 November."
  }
}

curl -X POST https://api.slurry.io/v1/simulations/acme-jira/actions -H "Authorization: Bearer $SLURRY_ACCOUNT_KEY" -H "Content-Type: application/json" -d '{
  "action": "jira.slip",
  "actor": "ivan.kirkbride@acme.example",
  "target": { "collection": "issue", "where": [{ "field": "fields.project.key", "op": "eq", "value": "UWP" }, { "field": "fields.status.name", "op": "ne", "value": "Done" }], "count": 3 },
  "params": { "days": 14, "text": "Moving the date: the vendor drop is late again." }
}'

# keep going in the same session, then keep it as a test case
curl -X POST https://api.slurry.io/v1/runs/$SESSION/save-as-case -H "Authorization: Bearer $SLURRY_ACCOUNT_KEY" -H "Content-Type: application/json" -d '{ "suite": "delivery", "name": "UWP slips" }'

# run one case (or leave "case" out to run every case in order)
curl -X POST https://api.slurry.io/v1/suites/billing/runs -H "Authorization: Bearer $SLURRY_ACCOUNT_KEY" -H "Content-Type: application/json" -d '{ "case": "invoice-goes-past-due-then-is-paid", "trigger": "ci" }'

# wait up to 25 seconds at a time for it to finish
curl https://api.slurry.io/v1/runs/$RUN_ID/wait -H "Authorization: Bearer $SLURRY_ACCOUNT_KEY"

{ "id": "...", "state": "finished", "result": "passed",
  "summary": { "steps": { "total": 3, "applied": 3, "read": 1 }, "readLagMs": { "median": 2100 }, "expectations": { "passed": 4, "failed": 0 } },
  "report": "https://slurry.io/app/tests/runs/..." }

name: Slurry tests
on: [pull_request]
jobs:
  slurry:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      # start your system pointed at the suite's simulations here, then:
      - name: Run the Slurry suite
        env:
          SLURRY_ACCOUNT_KEY: ${{ secrets.SLURRY_ACCOUNT_KEY }}
        run: |
          RUN=$(curl -sf -X POST https://api.slurry.io/v1/suites/billing/runs \
            -H "Authorization: Bearer $SLURRY_ACCOUNT_KEY" -H "Content-Type: application/json" \
            -d '{"trigger":"ci","speed":60}' | jq -r .id)
          for i in $(seq 1 60); do
            R=$(curl -sf https://api.slurry.io/v1/runs/$RUN/wait -H "Authorization: Bearer $SLURRY_ACCOUNT_KEY")
            [ "$(echo "$R" | jq -r .state)" = finished ] && break
          done
          echo "$R" | jq '{result, summary, report}'
          [ "$(echo "$R" | jq -r .result)" = passed ]

Slurry-Signature: t=1792771200,v1=hex(hmac_sha256(signingSecret, t + "." + body))
Slurry-Event: run.finished

{ "type": "run.finished", "id": "...", "suite": "billing", "kind": "suite", "result": "failed", "trigger": "ci",
  "summary": { ... }, "report": "https://slurry.io/app/tests/runs/..." }