---
module: incident.processing-rules
title: Processing Rules
tab: Testing
order: 35
audience: dev
---

Frontend test checklist for **Processing Rules** (the incident app, `incident.bcos.dev`). Open the **Processing Rules** menu in the left sidebar and click through in the UI. Mark each row Pass or Fail.

## Set up
Log in at **incident.bcos.dev** — test accounts (all password `Passw0rd-d3v!`):

| Login | Role | Sees |
|-------|------|------|
| `bcos_a@bcos.dev` | Admin | All institutions (C1 + C2 + C3) |
| `msp_a@msp1.bcos.dev` | MSP admin | C1 + C2 only |
| `customer_a@customer1.bcos.dev` | Customer | C1 only · read-only |

Rules apply to **event types** (e.g. `CARD_READER_FAIL`, `CASSETTE_LOW`, `TCR_SENSOR_FAULT`) from the simulator devices **C1-ATM-001…**, **C1-TCR-001…** (and C2-/C3- for the other institutions).

## What to test

| # | Do this | ✅ Pass if |
|---|---------|-----------|
| 1 | As `msp_a`, open **Processing Rules** in the sidebar | The menu expands to **Opening Rules / Closing Rules / Event Exceptions**, and Opening Rules loads a table of rules |
| 2 | Log in as `customer_a` and look at the sidebar | There is **no Processing Rules menu at all** — customers can't see this screen |
| 3 | As `msp_a` on **Opening Rules**, click **+ Add Rule**, enter a name, pick an **Event Type**, action **Create Incident**, **Save** | Panel slides in from the right; after Save a green **"Rule created"** message shows and the new rule appears in the table |
| 4 | In that Add Rule panel, open the **Institution** dropdown | As `msp_a` only **C1 and C2** are listed (plus Global) — no C3. Repeat as `bcos_a`: **all of C1, C2, C3** appear |
| 5 | On a rule row, click the **Enabled** toggle | It flips to **Disabled**; switch the **Enabled / Disabled** sub-tabs and the rule now shows under **Disabled**, not Enabled |
| 6 | Click **Edit** on a rule, change the name, **Save Changes**, then click **History** | The new name shows in the table, and the History modal lists change entries (Created / Updated) |
| 7 | In the left filter sidebar, type a word in **Search** or pick an **Action** (e.g. Suppress) | The list narrows to matching rules, the count updates, and a filter tag / highlighted filter bar appears |
| 8 | Click **✦ Suggest a Rule**, paste a sample log line and/or a description, click **Get Suggestion** | A suggested rule with a **confidence %** and reasoning appears, offering **Publish Directly / Save as Draft / Edit First**. (If the status shows **Unavailable**, Adoons is down — not a rule bug) |
| 9 | Open the **Event Exceptions** tab | Unrecognised event types are listed grouped by type with counts, each with a **Dismiss all** button — no error/crash |
| 10 | Click **Delete** on a rule, then confirm | A confirm dialog appears; after confirming the rule disappears from the table |

**Report a fail with:** the row #, which login you used, and what you actually saw.
