Text & chatWrite
Design a risk-based test strategy
Choose testing effort based on system risk.
Use this prompt
What to provide
- System / change
1 input to replace
← All prompt libraries
Techotick / Prompt library
Text prompts
Explore 400 text prompts for writing, research, planning, coding and everyday tasks. Choose a goal, customise the inputs and check the response against your sources.
400 prompts to explore
Text & chatWrite
Turn requirements into test cases
Turn requirements into concrete verification scenarios.
Use this prompt
What to provide
- Requirements
1 input to replace
Text & chatAnalyse
Identify overlooked feature edge cases
Find boundary conditions likely to be overlooked.
Use this prompt
What to provide
- Feature
1 input to replace
Text & chatWrite
Write meaningful unit tests
Verify meaningful behaviour in an isolated unit.
Use this prompt
What to provide
- Code / behaviour
- Framework
2 inputs to replace
Text & chatPlan
Design integration tests across real boundaries
Verify interactions between real system components.
Use this prompt
What to provide
- Component boundary
- Requirements
2 inputs to replace
Text & chatWrite
Test critical user journeys end to end
Check critical user journeys through the application.
Use this prompt
What to provide
- Journeys
- Tool
2 inputs to replace
Text & chatWrite
Plan regression checks for a specific change
Target checks around the likely impact of a change.
Use this prompt
What to provide
- Change / diff
1 input to replace
Text & chatWrite
Prepare user acceptance testing scenarios
Prepare users to validate whether the system meets their needs.
Use this prompt
What to provide
- Release
- Business requirements
2 inputs to replace
Text & chatWrite
Write a reproducible bug report
Describe a defect so another person can reproduce it.
Use this prompt
What to provide
- Notes
1 input to replace
Text & chatWrite
Triage defects using impact and evidence
Rank defects using user impact and evidence.
Use this prompt
What to provide
- Bug list
1 input to replace
Text & chatWrite
Plan the first response to a service incident
Organise the first response to a service disruption.
Use this prompt
What to provide
- Symptoms / system
1 input to replace
Text & chatWrite
Write an incident status update
Communicate service impact without speculation.
Use this prompt
What to provide
- Audience
- Confirmed facts
2 inputs to replace
Give the prompt a useful brief
A text prompt is most useful when it names the task, supplies the source material and describes the result you need. Replace the square-bracket inputs with your own details before copying it into your tool.
Make a summary easier to check
For a meeting summary, provide the notes and ask for decisions, action owners and unresolved questions in separate sections. Tell the tool to mark missing owners as unknown. Compare the result with the original notes before sharing it.
Refine one thing at a time
If an answer is too broad, specify the audience or ask for a shorter format. If it adds facts that are absent from your source, ask it to use only the supplied material and identify gaps. Keep sensitive information out of examples unless you have permission to use it.
Questions about text prompts
Supply the information named by each input, such as the text to summarise, your audience or the required format. The preview updates as you fill in the fields. Unfilled brackets remain visible so you can spot missing context.
Yes, but check the instructions and examples first. Change the goal, source material and output format together, then review the response. A prompt tested for one task does not guarantee the same result elsewhere.