← Back to Kontasks
Flow Pollution: Test Data Not Cleaned Up
Investigation reveals 182 flows are mostly test data from unit tests
Output
⚠️ Flow Pollution Found: Test Data
Root Cause: Unit tests are creating flows in the production JSONL files and not cleaning them up.
Evidence
# Test data pattern matches in data files: gvflows.jsonl 282 matches gvdecisions.jsonl 246 matches gvedges.jsonl 610 matches ──────────────────────────── Total: 1,138 test records
Sample Test Flow Titles
✗ "Bulk Flow 0 test_1767950749694_wspzmm" ✗ "Stats Flow 1 test_1767950749733_1ezdiy" ✗ "Authentication Feature test_1767950749711_uom6nt" ✗ "Merged Flow" (test merge operations)
Real Flows (Legitimate)
✓ "DASHBOARD CONSOLE REQUEST from user \"johnathon\":" 30 turns, 30M tokens - this is real work!
Recommended Fix
1. Immediate: Purge test data from JSONL files
2. Tests should: Use a separate test data directory, OR clean up after themselves
3. Add safeguard: Check for test_ prefix and reject in production
Summary: You're right to be suspicious! Only ~1 legitimate flow exists. The other 181 are test pollution. I can clean these up by filtering out any flows with test_ in their titles.
Quick Actions
Original Request
No layout configured
Details
Type
General
Status
Completed
Scope
vibetools
Tags
flowstestingcleanup
Created
9 Jan 2026, 7:39 pm
Updated
9 Jan 2026, 7:39 pm
Timing
⏱️ 52.0s
0 tools
● TTFE 0%
● Thinking 100%
● Tools 0%
Created By
claude
📋 Claude's Context
Session
ses_d3abe491...
Raw Data
{
"id": "fa0af4ad-39b1-4573-9d36-90d49d37cfa2",
"type": "general",
"status": "completed",
"title": "Flow Pollution: Test Data Not Cleaned Up",
"description": "Investigation reveals 182 flows are mostly test data from unit tests",
"context": {
"output": "<div style=\"background:#1e1e1e;color:#e0e0e0;padding:20px;border-radius:8px;font-family:'Consolas','Monaco',monospace;\">\n<h2 style=\"font-family:sans-serif;color:#fff;margin:0 0 16px 0;\">⚠️ Flow Pollution Found: Test Data</h2>\n\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;border-left:3px solid #e06c75;margin-bottom:16px;\">\n <p style=\"margin:0;color:#e0e0e0;\"><strong>Root Cause:</strong> Unit tests are creating flows in the production JSONL files and not cleaning them up.</p>\n</div>\n\n<h3 style=\"font-family:sans-serif;color:#fff;margin:16px 0 12px 0;font-size:14px;\">Evidence</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;\">\n<span style=\"color:#7f848e;\"># Test data pattern matches in data files:</span>\n<span style=\"color:#e5c07b;\">gvflows.jsonl</span> <span style=\"color:#e06c75;\">282 matches</span>\n<span style=\"color:#e5c07b;\">gvdecisions.jsonl</span> <span style=\"color:#e06c75;\">246 matches</span>\n<span style=\"color:#e5c07b;\">gvedges.jsonl</span> <span style=\"color:#e06c75;\">610 matches</span>\n<span style=\"color:#7f848e;\">────────────────────────────</span>\n<span style=\"color:#c678dd;\">Total:</span> <span style=\"color:#e06c75;font-weight:bold;\">1,138 test records</span>\n</pre>\n\n<h3 style=\"font-family:sans-serif;color:#fff;margin:16px 0 12px 0;font-size:14px;\">Sample Test Flow Titles</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;\">\n<span style=\"color:#e06c75;\">✗</span> \"Bulk Flow 0 test_1767950749694_wspzmm\"\n<span style=\"color:#e06c75;\">✗</span> \"Stats Flow 1 test_1767950749733_1ezdiy\"\n<span style=\"color:#e06c75;\">✗</span> \"Authentication Feature test_1767950749711_uom6nt\"\n<span style=\"color:#e06c75;\">✗</span> \"Merged Flow\" <span style=\"color:#7f848e;\">(test merge operations)</span>\n</pre>\n\n<h3 style=\"font-family:sans-serif;color:#fff;margin:16px 0 12px 0;font-size:14px;\">Real Flows (Legitimate)</h3>\n<pre style=\"background:#2d2d2d;padding:16px;border-radius:6px;overflow-x:auto;line-height:1.6;\">\n<span style=\"color:#98c379;\">✓</span> \"DASHBOARD CONSOLE REQUEST from user \\\"johnathon\\\":\" \n <span style=\"color:#7f848e;\">30 turns, 30M tokens - this is real work!</span>\n</pre>\n\n<h3 style=\"font-family:sans-serif;color:#fff;margin:16px 0 12px 0;font-size:14px;\">Recommended Fix</h3>\n<div style=\"background:#2d2d2d;padding:16px;border-radius:6px;\">\n <p style=\"margin:0 0 8px 0;color:#e0e0e0;\"><strong>1. Immediate:</strong> Purge test data from JSONL files</p>\n <p style=\"margin:0 0 8px 0;color:#e0e0e0;\"><strong>2. Tests should:</strong> Use a separate test data directory, OR clean up after themselves</p>\n <p style=\"margin:0;color:#e0e0e0;\"><strong>3. Add safeguard:</strong> Check for <code style=\"background:#3d3d3d;padding:2px 6px;border-radius:3px;\">test_</code> prefix and reject in production</p>\n</div>\n\n<div style=\"margin-top:16px;padding:12px;background:#2d2d2d;border-radius:6px;border-left:3px solid #61afef;\">\n <p style=\"margin:0;color:#e0e0e0;font-size:13px;\"><strong>Summary:</strong> You're right to be suspicious! Only ~1 legitimate flow exists. The other 181 are test pollution. I can clean these up by filtering out any flows with <code style=\"background:#3d3d3d;padding:2px 6px;border-radius:3px;\">test_</code> in their titles.</p>\n</div>\n</div>",
"requestedAt": "2026-01-09T09:45:00.000Z",
"requestId": "727cfc32-2254-406c-8f2f-14a1f553867f",
"choices": [
{
"label": "Clean up test data",
"value": "Clean up the test data from the gvFlows, gvDecisions and gvEdges JSONL files - remove any entries with test_ patterns in their IDs or titles",
"primary": true
},
{
"label": "Fix test isolation",
"value": "Fix the unit tests to use isolated test data directories instead of polluting production data files"
},
{
"label": "Both fixes",
"value": "Clean up the test data AND fix the tests to use isolated directories"
}
],
"turnTiming": {
"totalMs": 51950,
"ttfeMs": 100,
"thinkingMs": 51850,
"toolExecutionMs": 0,
"toolCallCount": 0,
"thinkingPct": 100,
"toolsPct": 0,
"ttfePct": 0
}
},
"createdBy": "claude",
"createdAt": "2026-01-09T09:39:10.225Z",
"updatedAt": "2026-01-09T09:39:14.752Z",
"targetUser": "claude",
"requestId": "727cfc32-2254-406c-8f2f-14a1f553867f",
"scope": "vibetools",
"tags": [
"flows",
"testing",
"cleanup"
],
"sessionId": "ses_d3abe491-395",
"flowId": "flow_01KEGVRXHHK7E25VFSX4HCV289",
"flowLinks": [
{
"flowId": "flow_01KEGVRXHHK7E25VFSX4HCV289",
"edgeType": "evidence",
"createdAt": "2026-01-09T09:39:10.225Z"
}
]
}