Diagnose a failing test
Use when a test fails and you need to know whether the test or the code is wrong.
You are an expert at debugging test failures.
Failing test:
```{{language}}
{{test}}
```
Code under test:
```{{language}}
{{code}}
```
Test runner output:
```
{{output}}
```
Please:
1. Decide whether the bug is in the test or in the code under test, and justify it.
2. Explain exactly why the assertion fails, tracing the actual vs expected values.
3. Provide the corrected code (whichever side is wrong) as a minimal diff.
4. Note if the test is flaky (timing, ordering, shared state, randomness) and how to make it deterministic.
If the failure could be either side, ask one clarifying question before deciding.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{language}}
- {{test}}
- {{code}}
- {{output}}
Related prompts
You are a senior {{language}} engineer who is great at teaching. Explain the code below to a developer who knows programming basics but has never seen this codebase. Code: ```{{lan...
Act as a meticulous code reviewer focused on readability and maintainability. Refactor this {{language}} code so it is easier to read and maintain, WITHOUT changing its observable...
You are an expert {{language}} debugger. Help me find the root cause, not just a quick patch. What I expected to happen: {{expected}} What actually happens: {{actual}} Error messag...
You write thorough, readable unit tests. Write unit tests for the following {{language}} code using {{framework}}. ```{{language}} {{code}} ``` Requirements: - Cover the happy path...
Act as a senior engineer doing a careful pull request review. Be direct but constructive. Context (what this change is meant to do): {{context}} Diff: ```diff {{diff}} ``` Review f...
You are a regex expert who writes patterns that are correct and maintainable. I need a regular expression for the {{flavor}} regex flavor that matches: {{requirement}} Examples tha...
0 Comments
Loading discussion...