n8n-studio:plan-tests

Generate unit and integration test scenarios from n8n workflow design documents.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It reduces the time and guesswork needed to create reliable unit and integration test scenarios for n8n workflow development by turning a design document into concrete test plans and executable test files.

Core Features & Use Cases

  • Integration test scenario planning: produces a structured test plan doc for both unit (code node) and integration (workflow) coverage.
  • Deterministic unit test scaffolding: generates .test.js unit test files targeting code node functions with clear input/result expectations.
  • Execution-oriented integration test artifacts: creates integration test JSON files using workflow summary triggerDataFormat when available, and separates sub-workflow invocation verification from actual sub-workflow behavior.

Real-world use case: After designing a workflow update, you can generate a test plan (03-test-plan.md) plus unit test files and integration JSON scenarios so the verifier can run Test Execution for one workflow at a time and enforce boundaries for sub-workflow calls.

Quick Start

Ask an n8n-studio agent to plan and write integration test scenarios from your design document, and it will generate 03-test-plan.md along with unit and integration test files.

Frequently Asked Questions about n8n-studio:plan-tests

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

FAQPage Schema
How do I generate integration test scenarios from an n8n workflow design document?

You can generate unit test scaffolding for n8n code nodes by transforming your workflow design document into deterministic .test.js files. These files target specific code node functions with clear input and result expectations for isolated testing.

Does n8n workflow testing verify sub-workflow behavior during integration tests?

n8n workflow testing does not verify actual sub-workflow behavior during integration tests. It enforces sub-workflow verification boundaries by validating only the Execute Workflow node parameters, separating sub-workflow invocation checks from end-to-end execution.

What is the difference between unit tests and integration tests for n8n workflows?

Unit tests for n8n workflows target individual code node functions using generated .test.js scaffolding, while integration tests validate workflow-level execution using triggerDataFormat-driven JSON scenarios. Integration testing focuses on workflow Test Execution rather than end-to-end acceptance testing.

How do I create a test plan for n8n workflow updates?

To create a test plan for n8n workflow updates, input your updated workflow design into an n8n-studio agent. It generates a 03-test-plan.md document covering both unit and integration test coverage, along with corresponding executable test artifacts.

Can I use triggerDataFormat to generate deterministic test inputs for n8n workflows?

Yes, you can use triggerDataFormat to generate deterministic test inputs for n8n workflows. When triggerDataFormat is available in the workflow summary, the tool uses it to drive input generation for execution-oriented integration test JSON artifacts.