ln-631-test-business-logic-auditor

To identify framework tests, use an auditor to detect and flag tests validating external library behavior rather than custom code. This skill pinpoints tests for frameworks like Prisma, Express, and JWT that do not pertain to proprietary application logic.

Removing framework tests for Prisma or bcrypt eliminates redundant checks on external library functionality. This streamlines your test suite by ensuring your tests solely verify how your application logic uses these queries and operations.

Auditing your test suite for redundant axios or React hooks tests involves scanning for tests that only validate library behavior. The auditor flags these instances and provides explicit REMOVE decisions to optimize your codebase.

Yes, this test auditing approach works for projects using Express and JWT by specifically detecting tests that focus on these frameworks' native behaviors. It flags any test that misses your proprietary code to help maintain a focused suite.

Framework test detection identifies tests re-testing external library functionality instead of your custom application code. You need it during code refactoring or test optimization to remove misplaced tests and streamline the test suite.

The limitation of auditing tests for business logic is that it strictly targets tests validating external frameworks like Prisma, Express, bcrypt, JWT, axios, and React hooks. It provides REMOVE decisions but does not generate new tests for your proprietary code.