Behaviour or implementation?
A test that breaks every time you refactor.
Shortreviewdesign
Is this testing behaviour or implementation? Rewrite it as behaviour if it is the latter.
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Reviewing existing tests. Judging naming, mocking, and whether a test asserts behaviour or just the implementation.
Keep this one
Promptory saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free