Infoocode / Standard
Testing method
The setup, the attempt, the failure, and the retest.
A polished outcome without a test record is not evidence. Our work records the starting state, the exact version and environment, what we expected, what happened, and what changed after failure.
01
Before the test
The author defines the claim or task before running the product or workflow.
- Product, model, plan, license, version, build, or commit
- Device, operating system, browser, runtime, region, and account state
- Prerequisites, permissions, settings, costs, and input scenarios
- Expected result and the evidence needed to judge it
02
During the test
The author follows a documented path and retains useful evidence. Failures stay in the record. Paid, destructive, privacy-sensitive, or security-sensitive actions are identified before a reader reaches them.
- Observed outputs and checkpoints
- Errors, edge cases, retries, and workarounds
- Screenshots, logs, code, prompts, data, or result tables where useful
- Limits that narrow the conclusion
03
Before publication
Commands, code, and steps are rerun from the final rendered article. A different editor inspects the evidence, samples important claims, challenges the verdict, and confirms that the visible limitations match the record.