How do I identify tests that validate framework behavior instead of my business logic?▼
Test auditing detects tests validating Express, Fastify, Koa, ORM libraries, or crypto frameworks rather than your application logic. Run ln-631-test-business-logic-auditor on your Node.js test files to surface framework-focused tests with removal recommendations and severity scores.
Can I use this auditor with Prisma, Mongoose, Sequelize, or TypeORM tests?▼
Yes. The auditor scans tests for ORM library behavior across Prisma, Mongoose, Sequelize, and TypeORM, alongside Express, Fastify, Koa, bcrypt, argon2, JWT, axios, fetch, got, and React hooks, identifying which tests validate framework internals rather than business logic.
What output does the test auditor provide?▼
The auditor outputs a JSON artifact containing compliance score, total issues count, severity breakdowns, and a findings list per test with severity level, file location, test name, usefulness score, reasoning, removal recommendations, and effort estimates.
Why should I remove tests that validate framework behavior?▼
Framework tests duplicate vendor responsibility and add maintenance burden without protecting your business logic. Removing them focuses your test suite on code you own, reduces noise in CI/CD, and surfaces gaps in actual application coverage.
Does the auditor work with existing test frameworks and refactoring workflows?▼
Yes. The auditor operates within the ln-630/ln-631 coordination workflow, integrating with your existing test suite to flag framework tests and propose refactoring or deletion with actionable location and rationale data.
What frameworks and libraries does the auditor detect?▼
The auditor detects framework tests across Express, Fastify, Koa, Prisma, Mongoose, Sequelize, TypeORM, bcrypt, argon2, JWT, axios, fetch, got, and React hooks in Node.js backend and React projects.
