All 29 unit tests were green, yet it broke in 2 places in real n8n — E2E verification before shipping paid templates

Workflows & Nodes✍ TextPublished: Source: Zenn (n8n)

#n8n

Key point

Just before shipping a paid n8n template (a workflow that automatically detects subscriptions from Rakuten Card statement CSVs), an E2E verification was performed in a real n8n environment using Docker. Although all 29 unit tests passed, it was found that it broke in 2 places in the real environment.

During the development of a paid template that, when Rakuten Card statement CSVs are loaded into n8n, detects charges that are "2 or more times in separate months and almost the same amount" as subscriptions and lists them with annual conversion and cancellation page URLs, an E2E verification was performed just before shipping.

All 29 vitest unit tests for the detection logic were green, but in a real n8n environment on Docker, it was in a state where it definitely broke in 2 places. The cause for both was not the logic, but the current n8n security default values.

This item is a summary. The full, checkable version is at the original source:

Read the original at Zenn (n8n) ↗