MethodTechnology & DevelopmentCode qualityStarter

Write automated tests

A test plan and test code covering happy paths, edge cases and failures.

This is a practical, copy-paste process for adding tests to new or legacy code.. Use it when you want a clear structure, then add your own details and the linked evidence.

Published by Deepstory Research. Reviewed Sep 2026.

How to use this method

1. Copy or downloadCopy the prompt below, or download the method file and attach it to your chat.
2. Paste into any AIChatGPT, Claude, Gemini or Copilot. Replace each [PLACEHOLDER] with your details, or let the AI ask you.
3. Add evidenceAttach the evidence files listed on this page so the AI works from sourced numbers, not guesses.

The prompt

Paste it as-is. The AI will ask for anything still in [BRACKETS].

Download .md

# Write automated tests
Method by Deepstory Research: deepstoryresearch.com/method/write-tests

You are a test engineer. Follow the method below step by step. Goal: A test plan and test code covering happy paths, edge cases and failures.

## My inputs
- Code under test: [CODE_UNDER_TEST]  (example: paste)
- Test framework: [TEST_FRAMEWORK]  (example: Jest, Vitest, pytest)
- Behaviour spec: [BEHAVIOUR_SPEC]  (example: acceptance criteria)

Before you start: if any input above is still in [BRACKETS] or missing, ask me for it in one short numbered list and wait. Do not guess. If I attached files (data, briefs, Deepstory evidence files), treat them as the primary source.

## Steps to follow
1. List behaviours to test.
2. Design cases: happy, edge, error.
3. Write tests with clear names.
4. Mock external dependencies only where needed.
5. Explain how to run them.

## Deliver the output in this structure
- Test plan
- Test code
- Run instructions
- Coverage gaps

## Quality rules
- Tests must fail if the behaviour breaks, no tautologies.
- Label every number as FACT (with source and date), ESTIMATE (show the calculation) or ASSUMPTION.
- If a Deepstory evidence file is attached, use its figures as the reference values and cite its source references; tag claims that are not from it as [UNVERIFIED].
- End with: the 3 assumptions that matter most, what would change the answer, and the single best next step.

What you need to give the AI

Input	Placeholder	Example
Code under test	[CODE_UNDER_TEST]	paste
Test framework	[TEST_FRAMEWORK]	Jest, Vitest, pytest
Behaviour spec	[BEHAVIOUR_SPEC]	acceptance criteria

Use it when

Adding tests to new or legacy code.

What you get

Test plan
Test code
Run instructions
Coverage gaps

The procedure, step by step

Read this before you run it, so you can check the AI actually followed the method.

1
List behaviours to test.
2
Design cases: happy, edge, error.
3
Write tests with clear names.
4
Mock external dependencies only where needed.
5
Explain how to run them.

Quality checks built into the prompt

• Tests must fail if the behaviour breaks, no tautologies.
• Every number labelled FACT, ESTIMATE or ASSUMPTION; claims outside attached evidence tagged [UNVERIFIED].

Evidence for this method

This method runs on your own material: your files, brief or code. If your task needs market or economic numbers, attach a sourced context file from the evidence library alongside the prompt.

Browse evidence

Run next

Methods that chain well after this one.

Technology & DevelopmentSet up a CI/CD pipelineA pipeline definition with build, test, security scan, preview and deploy stages.Technology & DevelopmentReview code with AIA structured code review for correctness, security, performance and readability, with concrete fixes.Technology & DevelopmentDebug a problem systematically with AIA reproduce → isolate → hypothesise → verify debugging session ending in a root cause and fix.Technology & DevelopmentWrite technical documentationREADME, setup, architecture and how-to docs written for the reader who will use them.

Deepstory methods are process guidance for AI tools. Review AI output before relying on it; legal, tax, medical and investment decisions need a qualified professional.