AI Prompts for Cursor for Unit Tests

Here is my code: [PASTE CODE]. What are the most important things to test? Identify the key behaviors, edge cases, and failure modes that unit tests should cover. Prioritize by risk.

What testing patterns and approaches should I use for this type of code: [DESCRIBE CODE TYPE: SERVICE LAYER / PURE FUNCTIONS / REACT COMPONENTS / API HANDLERS]? Recommend the right test structure.

For this module: [PASTE CODE], what test coverage should I aim for? Which lines and branches are most critical to cover and which are lower priority? Be practical, not dogmatic about 100%.

Set up a test file for [FILE NAME] using [JEST / VITEST / PYTEST / OTHER]. Create the basic structure: imports, describe blocks for each function, and placeholder test cases I should fill in.

This code depends on [LIST DEPENDENCIES: DATABASE, EXTERNAL API, FILESYSTEM]. What should I mock and how? Suggest a mocking strategy that keeps tests fast and isolated without mocking too much.

Write unit tests for this function using [TESTING FRAMEWORK]: [PASTE FUNCTION]. Cover: the happy path, edge cases (empty input, null, boundary values), and error cases. Add a test for each.

Write unit tests for this class: [PASTE CLASS]. Test each public method, the constructor, state changes, and interaction between methods.

Write unit tests for this async function: [PASTE ASYNC CODE]. Cover: successful resolution, error/rejection handling, and any timeout or retry behavior. Use proper async testing patterns.

Write integration tests for this module that test multiple components working together: [PASTE CODE]. These should be slightly higher level than unit tests but still fast and deterministic.

Write tests for this code that mock its dependencies: [PASTE CODE WITH DEPENDENCIES]. Mock [LIST DEPENDENCIES] and test that the code correctly calls and handles responses from each.

Review these tests and tell me what they are missing: [PASTE TESTS]. Are they testing the right things? What edge cases are not covered? What would fail to catch common bugs?

Improve the readability of these tests: [PASTE TESTS]. Use descriptive test names, the Arrange-Act-Assert pattern, and clear assertions. Rename vague test descriptions.

These tests have a lot of duplicated setup code: [PASTE TESTS]. Refactor them to use [BEFOREEACH / TEST FIXTURES / PARAMETERIZED TESTS] to reduce repetition while keeping clarity.

Convert these similar test cases into a parameterized test: [PASTE REPEATED TEST CASES]. Use [TEST.EACH / PYTEST.MARK.PARAMETRIZE / EQUIVALENT] to test all the cases with less code.

This test is flaky — it sometimes passes and sometimes fails: [PASTE TEST]. What are the most likely causes of flakiness here, and how do I fix it?

I want to build [FEATURE] using TDD. Before I write any implementation code, write the tests that define what the code should do. Use [TESTING FRAMEWORK]. I'll implement the code to make these pass.

My current test coverage is [X]% and I want to reach [Y]%. Here are the uncovered lines: [PASTE COVERAGE REPORT EXCERPT]. Write tests specifically targeting the uncovered code.

I have repeated patterns in my tests: [DESCRIBE THE PATTERN]. Create test helper functions or factories that reduce this duplication without making tests harder to understand.

Write a brief testing strategy document for this codebase: [DESCRIBE PROJECT]. Cover: what we test, how, what we mock, coverage goals, and how to run tests. Keep it under one page.

Review the tests in this PR: [PASTE TESTS]. Does the test coverage match the scope of the code changes? Are the right things being tested? Suggest any missing test cases.