n8n-testing

n8n Testing Skill

This skill ensures workflows are thoroughly tested before production activation.

When to Activate

• Before activating any workflow
• After making changes to existing workflows
• When debugging failed executions
• Before deploying to production environment

Execution Modes

Manual Execution (Development)

Use for testing during development:

• Run workflows with "Execute Workflow" button
• Keep workflow Inactive while developing
• Iterate and test node by node
• See data transformations in real-time

Production Execution (Live)

Workflows run automatically when:

• Set to Active
• Triggered by webhooks, schedules, or events

Rule: Never develop on Active workflows.

Testing Workflow

1. Data Pinning

Pin data to ensure consistent testing:

Benefits:

• Avoid repeated requests to external systems
• Save API rate limits during development
• Consistent data for all test runs
• No need to trigger external events

How to Pin:

1. Execute node once to get real data
2. Click "Pin" on node output
3. Future executions use pinned data

Limitations:

• Only for nodes with single main output
• Not available in production executions
• Development feature only

2. Node-by-Node Testing

Test each node individually:

Step 1: Test Trigger node
        ↓ Verify output
Step 2: Test Processing node
        ↓ Verify transformation
Step 3: Test Output node
        ↓ Verify final result

3. Test with Sample Data

Create test data in Code node:

// Test data for development
return [
  {
    json: {
      id: 'test-001',
      email: '[email protected]',
      amount: 100,
      status: 'pending'
    }
  },
  {
    json: {
      id: 'test-002',
      email: 'invalid-email',  // Test validation
      amount: -50,             // Test edge case
      status: 'active'
    }
  }
];

4. Edge Case Testing

Test these scenarios:

Scenario	Test Data	Expected
Empty input	[]	Graceful handling
Null values	{ email: null }	Validation error
Large payload	1000+ items	No timeout
Invalid format	{ email: 'not-email' }	Rejection
Missing fields	{ id: '1' }	Validation error
Special characters	{ name: '<script>' }	Sanitized