Plan tests around a deletion deadline
Using Claude where available: Supply example rules, synthetic records and a time zone to cover before, at and after the deadline.
Execution environment and usage
AI / software
General text chat (example: Claude); original stack retained below
Where to operate
A general text conversation, for example a new chat at claude.ai where available. This is the suggested exercise entry, not an attribution of the original tool.
Getting started
- Open claude.ai or another text-chat tool you are authorized to use.
- Convert the required material below into readable, source-labeled text and paste only necessary authorized excerpts.
- Enter the case prompt and check the resulting draft against the original material.
Setup and plan requirements
Isolated example or code excerpt, synthetic records, precise time rules and clock/timezone. Text chat requires an available account and allowance; Claude has location and age requirements. Manually transcribe images or scans first rather than assuming text chat can inspect the original file.
Prompt portability limits
Current output is a test plan. Running tests or modifying a repository needs configured code environment; no Jules account required for planning.
Usage limitations
This review performed no installation, hands-on test or regional-availability check. Author page retrieved; supplied record names Google Jules, not an unnamed tool.
Environment sources
適用情境 / When to use
Use the plan to compare interface feedback with server enforcement, including stale screens and direct requests. It needs no Jules account and does not delete records, edit code or deploy changes. The article does not report comprehensive passing results. The original tool is Google Jules, classified here as Other or custom.
步驟 / Steps
- Use an isolated example, synthetic records and explicit time rules.
- Test before, at and after the boundary with a defined timezone and clock source.
- Check consistency between interface state and backend rejection.
提示詞 / Prompt
Using [isolated example/synthetic records/time rules/timezone and clock source], draft deletion-permission tests. Cover before, at and after boundaries, stale screens and direct requests. Separate interface feedback from backend enforcement. Write a test plan only; do not delete data, push or deploy.
留意事項 / Cautions
- Use synthetic data only and perform no real deletion.
- Derive time limits from requirements rather than copying the source’s duration.
來源限制 / Evidence limits
Generated tests do not establish correct time limits or backend authorization.
流程說明 / Workflow note
These steps and prompts are original, untested exercises by this site, not the author’s verbatim workflow. Reported results do not guarantee exercise outcomes.
原始工具組合 / Original tool stack
Google Jules
Source publication date: 2025-05-22
Source checked: 2026-10-20