Mock Data Schema Mismatch in Cursor-Generated Tests

Tests generated by Cursor use mock data objects that don't match the actual schema of your database models, API responses, or TypeScript interfaces. The mocks have missing required fields, wrong data types, extra properties that don't exist, or outdated schema versions that don't reflect recent changes to your models.

This schema mismatch means tests pass with incorrect data structures, giving false confidence. A test might verify that a function handles a user object correctly, but the mock user is missing the role field that your actual code checks — so the test passes while the real code would fail. Alternatively, tests fail because the mock triggers validation errors from mismatched types.

The problem is insidious because it's not always obvious. Tests may pass for months until a code path that accesses the missing or mistyped field is finally triggered in production.