n8n-studio:run-verification

Execute n8n integration test scenarios and compare outputs against expected JSON results.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/icednut/n8n-studio --skill n8n-studio-run-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-studio:run-verification
Source: https://github.com/icednut/n8n-studio/tree/main/skills/run-verification
Command: npx skills add https://github.com/icednut/n8n-studio --skill n8n-studio-run-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of reliably validating n8n workflow changes by executing all integration test scenarios and comparing actual outputs to expected results.

Core Features & Use Cases

  • Integration scenario execution: Loads all JSON scenarios from workflow/[프로젝트명]/test/integration/ and runs each scenario against the target input.workflowId.
  • Expected vs actual verification: Compares runtime outputs to expectedOutput (including JSON structure/value matching) and records clear failure reasons.
  • Sub-workflow call validation: Verifies whether specified "Execute Workflow" sub-workflow nodes were called and whether their input data matched expected inputs, without validating the sub-workflow outputs themselves.
  • Result reporting: Produces a human-readable pass/fail report including per-scenario outcomes, expected/actual details on failure, and an optional sub-workflow verification table.

Quick Start

Ask an n8n-studio agent to run all integration test scenarios for the current workflow and return a pass/fail report with any failing scenarios explained in detail.

Frequently Asked Questions about n8n-studio:run-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run integration tests for n8n workflows and compare expected vs actual outputs?

n8n workflow verification loads JSON test scenarios from the integration directory, executes each against the target input workflowId, and performs expected-vs-actual JSON comparison to generate a structured pass/fail report.

Can I validate sub-workflow calls and node-level inputs in n8n integration testing?

Sub-workflow validation verifies whether Execute Workflow nodes were called and whether their node-level input data matched expected inputs, without validating the sub-workflow outputs themselves, providing targeted sub-workflow verification.

What format do integration test scenarios need to be in for n8n workflow verification?

Integration test scenarios are defined as JSON input files containing expected output types, loaded automatically from the project test directory to drive n8n Test Execution and expected-vs-actual comparison workflows.

How does expected vs actual comparison work when verifying n8n workflows?

Expected vs actual comparison matches runtime outputs against defined expectedOutput values using JSON structure and value matching, recording clear failure reasons to produce a human-readable pass/fail report.

What details are included in an n8n test execution pass/fail report?

The pass/fail report includes per-scenario outcomes, expected and actual output details on failure, and an optional sub-workflow verification table matching Execute Workflow node inputs, producing a human-readable test execution summary.