Start With The Reason To Recheck
A new announcement does not mean every earlier check is invalid. Identify what changed in the product or your own task, then choose the relevant check. For example, a different input format may call for another output test; changed account permissions need a separate permissions review.
Read the applicable official notice before assuming a change reaches your account. Aiplorer records selected announcements, not a complete change history for every service.
Preserve The Previous Result First
Before clearing completed checks, keep a dated summary of what you actually tested, what failed, and what remains unresolved. Store full evidence in an approved location. A browser-local note is a short reminder, not an evidence archive or a revision history.
For illustration only, an earlier note might say:
Prior test: three invented request messages. IDs were retained, but a proposed date became a confirmed deadline. Do not use that output as an agreed work plan. Next: try an explicit missing-value instruction.
This is a fictional example, not a result from a named service. Your own note should describe your actual run, not copy an example as evidence.
Use a shortlist backup when you need a separate copy before editing. A backup may contain your private notes; keep it in an approved location and do not publish it. Restoring a backup replaces local evaluation data rather than merging a history of tests.
Clear Only What You Intend To Revisit
If just one question needs another look, uncheck that item. If you want to revisit all four candidate checks, Reset checks asks for confirmation and clears only that saved tool’s checked boxes.
The reset preserves:
- The tool in your saved list and its decision stage.
- Its private note and previously recorded local test date.
- Other candidates and their checks.
- Announcement read status.
It does not archive the previous checked boxes or create a new test record. Cancel leaves the checks unchanged. If the page cannot verify the reset was saved, review the displayed state rather than assuming it succeeded.
Keep Old Evidence Separate From The Next Result
The previous test date remains a previous test date. Change it only after you actually run another test. A reset does not move a candidate out of Ready to decide; choose Testing yourself when that matches your current decision stage.
Do not re-check output, privacy or plan items just to make progress look complete. Each check answers a different question. “Could not test” is a useful observation when a required setting, account or input is unavailable.
For the fictional request exercise, the next note could record:
Next run: use the same three invented messages and preserve the original result separately. Check whether proposed dates remain unconfirmed. Record the actual outcome and human corrections before changing the date.
Make The Next Visit Specific
Return to your shortlist with one unresolved question, not a requirement to complete every box. Try the missing-value extraction exercise or the before-and-after retest. Checklists are private reminders, not scores or proof of general reliability.