Original tests and aggregation: separate execution evidence from source review
Compare claims supported by first-hand testing and source synthesis, checking versions, inputs and failures for credible reviews.
Choose an approach
Use first-hand evidence for behavior under specific settings and labeled synthesis for product scope and documentation. Combine them without calling unexecuted steps tests or presenting others’ screenshots as your own. Define supported claims and disclose whether evidence comes from operation or source review.
Test records and documentation support different scopes
Google’s review guidance values first-hand evidence and decision factors, while helpful-content guidance values more than rewriting. Documentation supports stated capabilities, not successful execution on a device. One test covers its version and inputs, not all users. Preserve limits for latency, quality and cost and avoid generalizing examples into universal performance.
Check inputs, outputs and evidence boundaries for one task
For an executed task, preserve public input, versions, commands or settings and full output, then validate the file. For source reviews, verify each capability and phrase tests as proposals. Match comparison conditions and leave unrun options unverified. Record failures and manual fixes rather than only selected successes. This page is documentation-based and reports neither product trials nor traffic gains from writing styles.
Maintain original evidence rather than adding adjectives
Revalidate important changes after tool updates and date the review. Update source summaries and remove obsolete capabilities. Count evidence retention and corrections. Begin with documented scope and test decisions that matter most rather than portraying every feature as personal experience. Trace conclusions to evidence and preserve unknowns instead of claiming comprehensive tests that never occurred.
Checked sources
These sources support the concepts and methods described here. Examples and test scope are labeled separately; check the version of the tools you use.