n8n Output Regression

--- name: n8n-output-regression description: Run real n8n output regression tests with complete JSON fixtures and expected item counts, ordered IDs, fields or full JSON. Use when a successful workflow loses rows, changes recipients or text, or when preserving output across a workflow edit or version upgrade. license: MIT-0 version: 0.1.9 metadata: openclaw: requires: bins: [node, npx] homepage: https://github.com/blucca/n8n-check/tree/v0.1.9/skills/n8n-output-regression --- # n8n output regression Turn the intended output into a saved contract, run it on real n8n, and keep the same case when fixing the workflow. This uses the free, AI-led [n8n-check project](https://github.com/blucca/n8n-check). ## 1. Establish the contract Read the workflow export and the task's expected behavior. Pick: - A **fixture boundary**: the node whose output is replaced by the complete batch of input JSON objects. - An **output node**: the executed transformation whose result matters. - The expected count, ordered IDs/field values, or complete JSON objects. Use the user's requirement or an approved golden result; review exported pins before adopting them as expectations. Keep every input item in the fixture, including a useful distractor. Request the missing expected behavior when the task leaves it open. For a transformation between external systems, stop after its output; reads and final delivery keep separate integration contracts. Independently reachable sibling branches remain in the slice. ## 2. Draft and review the case locally Node 24+ runs the versioned generator. The commands in this section read/write local JSON; n8n execution happens in section 3. Draft a case from the export's pins: ```sh npx --yes @blucca/n8n-check@0.1.9 init workflow.json \ --input "Read invoices" --assert "Prepare notification" \ --stop-after "Prepare notification" --out workflow.case.json ``` Replace these node names with the selected names from the actual export. Review the draft's readiness messages, edit the fixture/expectation, and retain `version`, `name`, `input`, `mocks`, and `assertions`. `input.items` contains plain JSON objects; the runner wraps them as n8n items. For a two-invoice task whose required ordered IDs are `INV-42`, `INV-43`, a field-and-count contract is: ```json { "version": 1, "name": "Keep both invoice IDs before delivery", "input": { "node": "Read invoices", "items": [ { "invoiceId": "INV-42", "totalCents": 65000 }, { "invoiceId": "INV-43", "totalCents": 12050 } ] }, "stopAfter": "Prepare notification", "mocks": [], "assertions": [{ "node": "Prepare notification", "count": 2, "pluck": "json.invoiceId", "equals": ["INV-42", "INV-43"] }] } ``` Use full-object `equals` for notification text/amounts too; the [complete invoice case](https://github.com/blucca/n8n-check/blob/main/examples/stop-after/case.json) checks both exact messages. Arrays preserve order and duplicates; object-key order is ignored. ## 3. Execute the reviewed contract ### A. Your existing n8n editor — versioned local generation ```sh npx --yes @blucca/n8n-check@0.1.9 editor-test workflow.json workflow.case.json \ --out n8n-editor-test.json ``` This emits a separate inactive workflow locally using the published generator. Review its fixture, retained nodes and expected-output oracle, import it into your n8n editor, then **Execute workflow**. The original export stays unchanged. The generated **Check expected output** branch returns `status: "passed"` or throws on a mismatch. Leave it below the tested branch: it runs last, including when zero items skip downstream nodes. Editor tests cover local JSON transforms, v1 execution order, and one incoming connection per node. [Five native controls and their actual results](https://github.com/blucca/n8n-check/tree/main/examples/editor-tests). ### B. CLI or CI — network-isolated execution Merge/loops/waits and HTTP mocks use this route for a self-contained slice. Test saved-ID child calls as a self-contained child/downstream export; a complete call graph needs its referenced-workflow setup separately. Build the pinned runner image, then run from the directory containing your test export and case: ```sh git clone --depth 1 --branch v0.1.9 https://github.com/blucca/n8n-check n8n-check-tool docker build -t n8n-check:0.1.9 n8n-check-tool docker run --rm --network none -v "$PWD:/work" n8n-check:0.1.9 \ workflow.json workflow.case.json --out /work/regression-results --json ``` On Linux, add `--user "$(id -u):$(id -g)"` to `docker run` if your ID differs from the image's default 1000. [GitHub Action route](https://github.com/blucca/n8n-check#add-a-check-to-github-actions). The runner executes the selected slice with fresh fixture input and cleared output pins. HTTP mocks test the actual Request node's method, body and retry behavior; actual provider state/delivery use separate integration checks. ## 4. Read the result, fix, and rerun For **test execution** (`init` writes a draft; `editor-test` writes a test workflow): - Exit **0**: the contract passed. - Exit **1**: regression or execution failure; read `checks`, `error`, and the first expected/actual mismatch. - Exit **2**: setup/configuration error; fix the reported setup before evaluating the output. Keep the case fixed while editing the workflow. Verify the check is active with one controlled wrong expected ID/count, then restore the approved expectation. For a known regression, rerun the original and repaired exports with the same case. [Both example n8n executions succeed while one drops an invoice](https://github.com/blucca/n8n-check/tree/main/examples/stop-after). [Author-run command checks](example-results.json): CLI 0.1.8 external assertions catch the one-ID regression while both engine executions succeed. Locally generated 0.1.9 editor tests pass the two-ID output and throw on the one-ID output in n8n 2.41.7. Deliver the workflow/test export, reviewed case, actual n8n version, result and first mismatch. CLI writes `report.json` and `junit.xml` under the output directory; keep the report with the case for the next edit or upgrade. State the tested boundary and the integration work remaining.

存档时间线

版本索引永久保留；内容副本只保留最新 1 份，更早版本仅留索引与哈希（存档时间线的证据链不会因此断裂）。

下载存档内容副本