n8n:reproduce bug

Engineering Community

Skill notes

Step 1: Parse Signals

Extract the following from the provided ticket context: Error message / stack trace (if provided) Reproduction steps (if provided) Workflow JSON (if attached) Affected area (node, execution engine, editor, API, config, etc.)

Step 2: Route to Test Strategy

Based on the affected area, pick the test layer and pattern: Area · Test Layer · Pattern · Key Location Node operation · Jest unit · NodeTestHarness + nock · packages/nodes-base/nodes/*/test/ Node credential · Jest unit · jest-mock-extended · packages/nodes-base/nodes/*/test/ Trigger webhook · Jest unit · mock IHookFunctions + jest.mock GenericFunctions · packages/nodes-base/nodes/*/test/

Step 3: Locate Source Files

Find the source code for the affected area: Search for the node/service/component mentioned in the ticket Find the GenericFunctions file (common bug location for nodes) Check for existing test files in the same area Look at recent git history on affected files (git log --oneline -10 -- <path>)

Step 4: Trace the Code Path

Read the source code and trace the execution path that triggers the bug: Follow the call chain from entry point to the failure Identify the specific line(s) where the bug manifests Note any error handling (or lack thereof) around the bug

Step 5: Form Hypothesis

State a clear, testable hypothesis: "When [input/condition], the code does [wrong thing] because [root cause]" Identify the exact line(s) that need to change Predict what the test output will show

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@n8n-io · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
Node.js
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Parse Signals

Extract the following from the provided ticket context: Error message / stack trace (if provided) Reproduction steps (if provided) Workflow JSON (if attached) Affected area (node, execution engine, editor, API, config, etc.)

02
Step 2: Route to Test Strategy

Based on the affected area, pick the test layer and pattern: Area · Test Layer · Pattern · Key Location Node operation · Jest unit · NodeTestHarness + nock · `packages/nodes-base/nodes/*/test/` Node credential · Jest unit · jest-mock-extended · `packages/nodes-base/nodes/*/test/` Trigger webhook · Jest unit · mock IHookFunctions + jest.mock GenericFunctions · `packages/nodes-base/nodes/*/test/`

03
Step 3: Locate Source Files

Find the source code for the affected area: Search for the node/service/component mentioned in the ticket Find the GenericFunctions file (common bug location for nodes) Check for existing test files in the same area Look at recent git history on affected files (`git log --oneline -10 -- <path>`)

04
Step 4: Trace the Code Path

Read the source code and trace the execution path that triggers the bug: Follow the call chain from entry point to the failure Identify the specific line(s) where the bug manifests Note any error handling (or lack thereof) around the bug

05
Step 5: Form Hypothesis

State a clear, testable hypothesis: "When [input/condition], the code does [wrong thing] because [root cause]" Identify the exact line(s) that need to change Predict what the test output will show

06
Step 6: Find Test Patterns

Look for existing tests in the same area: Check `test/` directories near the affected code Identify which mock/setup patterns they use Use the same patterns for consistency If no tests exist, find the closest similar node/service tests as a template

07
Step 7: Write Failing Test

Write a regression test that: Uses the patterns found in Step 6 Targets the specific hypothesis from Step 5 Includes a comment referencing the ticket ID Asserts the CORRECT behavior (test will fail on current code)

08
Step 8: Run and Score

Run the test from the package directory (e.g., `cd packages/nodes-base && pnpm test <file>`). Classify the result: Confidence · Criteria · Output CONFIRMED · Test fails consistently, failure matches hypothesis · Reproduction Report LIKELY · Test fails but failure mode differs slightly · Report + caveat

09
Step 9: Iterate or Bail

If UNCONFIRMED after first attempt: Revisit hypothesis — re-read the code path Try a different test approach or layer Maximum 3 attempts before declaring UNCONFIRMED Hard bailout triggers (stop immediately):

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.