JavaScript Node.js Stream & Buffer Unit Test Suite Generator
Generate unit tests asserting backpressure, chunked buffering, stream pipeline errors, and drain events in Node.js.
Compatibility & Specs
Compatible AI Models
ClaudeChatGPTGemini
Last UpdatedOct 3, 2026
Customizable Variables3 parameters
Main Prompt Template
140 words • 1045 characters
You are a Principal Node.js Core Engineer and Test Specialist. I need a comprehensive unit test suite verifying a custom Node.js Stream or Buffer processing pipeline.
Custom Stream / Buffer Code to Test:
[stream_code]
Testing Framework (Vitest, Jest, Node Test Runner):
[test_runner]
Expected Backpressure & Error Scenarios:
[stream_scenarios]
Deliver an exhaustive Stream Test Suite:
1. Stream Boundary & Chunking Matrix: Test cases covering clean stream completion, chunk boundary splits, empty chunks, and premature stream destruction (`stream.destroy(err)`).
2. Backpressure & HighWaterMark Verification: Explicit test demonstrating that when a downstream consumer pauses or slows down, the transform stream respects backpressure and stops pulling from source.
3. Pipeline Error Propagation: Verify that an error thrown mid-stream is safely propagated through `pipeline()` without leaking file descriptors or open socket handles.
4. Complete Production Test Code: Clean, executable test code with mock readable/writable helper utilities.
Tip:Variables marked in purple brackets can be tailored below.
Customize Prompt
Fill in the variables below. Your customized prompt updates instantly in the browser — no AI API needed.
Parameters (3)* Indicates required field
[stream_code]
The Transform, Readable, or Writable stream class/function
[test_runner]
Vitest, Jest, or native node:test
[stream_scenarios]
Backpressure, corrupt JSON lines, partial chunking
3 parameters active
Live Customized OutputLive Preview
230 wordsYou are a Principal Node.js Core Engineer and Test Specialist. I need a comprehensive unit test suite verifying a custom Node.js Stream or Buffer processing pipeline.
Custom Stream / Buffer Code to Test:
import { Transform } from 'node:stream';
export class LineBreakJsonParser extends Transform {
constructor(options) {
super({ ...options, objectMode: true });
this._buffer = '';
}
_transform(chunk, encoding, callback) {
this._buffer += chunk.toString();
const lines = this._buffer.split('\n');
this._buffer = lines.pop() || '';
for (const line of lines) {
if (line.trim()) this.push(JSON.parse(line));
}
callback();
}
_flush(callback) {
if (this._buffer.trim()) {
this.push(JSON.parse(this._buffer));
}
callback();
}
}
Testing Framework (Vitest, Jest, Node Test Runner):
Vitest with TypeScript.
Expected Backpressure & Error Scenarios:
1. Chunks split across JSON boundaries (half a JSON string in chunk 1, rest in chunk 2). 2. Corrupt JSON syntax throws error. 3. Final un-terminated line flushed correctly.
Deliver an exhaustive Stream Test Suite:
1. Stream Boundary & Chunking Matrix: Test cases covering clean stream completion, chunk boundary splits, empty chunks, and premature stream destruction (`stream.destroy(err)`).
2. Backpressure & HighWaterMark Verification: Explicit test demonstrating that when a downstream consumer pauses or slows down, the transform stream respects backpressure and stops pulling from source.
3. Pipeline Error Propagation: Verify that an error thrown mid-stream is safely propagated through `pipeline()` without leaking file descriptors or open socket handles.
4. Complete Production Test Code: Clean, executable test code with mock readable/writable helper utilities.
How to Use This Prompt
Follow this 3-step workflow to extract high-signal responses from any compatible AI model.
01
1. Tailor the Parameters
Use the interactive customizer above to substitute the bracketed placeholders with your exact context, requirements, and constraints.
02
2. Send to AI Model
Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot. These models follow structured multi-step constraints reliably.
03
3. Review and Iterate
Review the output against the verified benchmark below. Follow up in the conversation to stress-test edge cases or refine tone.
Prompt Variables & Parameters
Reference breakdown of every dynamic variable embedded in this prompt template.
| Placeholder | Parameter Name | Type | Status | Description & Guidance |
|---|---|---|---|---|
| [stream_code] | Custom Stream Code | textarea | Required | The Transform, Readable, or Writable stream class/functionDefault: import { Transform } from 'node:stream'; export class LineBreakJsonParser extends Transform { constructor(options) { super({ ...options, objectMode: true }); this._buffer = ''; } _transform(chunk, encoding, callback) { this._buffer += chunk.toString(); const lines = this._buffer.split('\n'); this._buffer = lines.pop() || ''; for (const line of lines) { if (line.trim()) this.push(JSON.parse(line)); } callback(); } _flush(callback) { if (this._buffer.trim()) { this.push(JSON.parse(this._buffer)); } callback(); } } |
| [test_runner] | Test Runner | text | Required | Vitest, Jest, or native node:testDefault: Vitest with TypeScript. |
| [stream_scenarios] | Scenarios to Verify | textarea | Required | Backpressure, corrupt JSON lines, partial chunkingDefault: 1. Chunks split across JSON boundaries (half a JSON string in chunk 1, rest in chunk 2). 2. Corrupt JSON syntax throws error. 3. Final un-terminated line flushed correctly. |
Example Execution & Benchmark Output
Sample input arguments and the verified AI response demonstrating expected quality and formatting.
Sample VariablesInputs
[stream_code]
import { Transform } from 'node:stream';
export class LineBreakJsonParser extends Transform {
constructor(options) {
super({ ...options, objectMode: true });
this._buffer = '';
}
_transform(chunk, encoding, callback) {
this._buffer += chunk.toString();
const lines = this._buffer.split('\n');
this._buffer = lines.pop() || '';
for (const line of lines) {
if (line.trim()) this.push(JSON.parse(line));
}
callback();
}
_flush(callback) {
if (this._buffer.trim()) {
this.push(JSON.parse(this._buffer));
}
callback();
}
}
[test_runner]
Vitest with TypeScript.
[stream_scenarios]
1. Chunks split across JSON boundaries (half a JSON string in chunk 1, rest in chunk 2). 2. Corrupt JSON syntax throws error. 3. Final un-terminated line flushed correctly.
Expected AI ResponseVerified Result
### Stream & Buffer Vitest Suite
```typescript
import { describe, it, expect } from 'vitest';
import { Readable } from 'node:stream';
import { pipeline } from 'node:stream/promises';
import { LineBreakJsonParser } from './json-parser';
describe('LineBreakJsonParser Stream', () => {
it('should parse JSON lines split across arbitrary chunk boundaries', async () => {
const parser = new LineBreakJsonParser();
const results: any[] = [];
parser.on('data', obj => results.push(obj));
// Simulate network chunks splitting JSON mid-string
const source = Readable.from([
Buffer.from('{"id": 1, "na'),
Buffer.from('me": "Alice"}\n{"id": 2, "name": "Bob"}\n')
]);
await pipeline(source, parser);
expect(results).toEqual([
{ id: 1, name: 'Alice' },
{ id: 2, name: 'Bob' },
]);
});
it('should cleanly flush the final JSON line even without trailing newline', async () => {
const parser = new LineBreakJsonParser();
const results: any[] = [];
parser.on('data', obj => results.push(obj));
const source = Readable.from([Buffer.from('{"id": 42}')]);
await pipeline(source, parser);
expect(results).toEqual([{ id: 42 }]);
});
it('should emit error and stop pipeline when invalid JSON syntax is encountered', async () => {
const parser = new LineBreakJsonParser();
const source = Readable.from([Buffer.from('{"id": NOT_VALID_JSON}\n')]);
await expect(pipeline(source, parser)).rejects.toThrow(SyntaxError);
});
});
```
Best Use Cases
Scenarios and roles where this prompt produces maximum leverage.
Node.js developers building custom ETL transform pipelines and file parsers
Engineers validating backpressure and memory safety on high-throughput data streams
Backend teams testing stream error propagation through `node:stream/promises` pipelines
Tips for Best Results
Techniques to elevate response fidelity
- •Specify your exact runtime and dependency versions (e.g. Next.js 15, React 19, TypeScript 5.4) to eliminate outdated syntax hallucinations.
- •Ask the model to enumerate potential runtime failure modes, concurrency issues, or null boundary states before generating code.
- •Request idiomatic, type-safe solutions with clear unit test skeletons rather than monolithic scripts.
Common Mistakes to Avoid
Frequent failure modes and anti-patterns
- •Pasting large unformatted code dumps without indicating the specific function or error you want analyzed.
- •Deploying AI-generated code directly to production without verifying memory safety, edge cases, and security vulnerabilities.
- •Omitting architectural constraints (such as SSR vs. client component boundaries or database indexing).
Part of Curated Collections
This prompt is sequenced as part of these goal-oriented workflows
Related AI Prompts
Complementary workflows in JavaScript
Codingintermediate
Algorithm Big-O Time & Space Complexity Optimizer
Profile nested iterations and un-indexed lookups to refactor O(N^2) algorithms into O(N) or O(N log N) implementations.
claudechatgptgemini
#algorithms#big-o#complexity-analysis
JavaScriptadvanced
Node.js Async Error Handling & Crash Resilience Auditor
Bulletproof Node.js backend services against unhandled promise rejections, streaming aborts, and zombie processes.
claudechatgpt
#nodejs#error-handling#backend
Codingintermediate
Edge-Case Driven Unit Test Suite Generator with Mocks
Generate thorough, resilient unit test suites targeting boundary conditions, error branches, and mock contracts.
claudechatgptgemini
#unit-testing#jest#vitest