What a test actually shows
Read the source and test notes on each guide. Some pages describe source code or settings; others describe a specific lab test. Finding a feature in code does not show that it is enabled or that a real call worked.
- Found in source: the code exists in the revision inspected.
- Configured: the relevant settings were present when checked.
- Enabled: the feature was turned on in the checked environment.
- Tested: the described test produced its stated result. A lab test does not establish production capacity or test another carrier.
Publication checklist
- State the tested revision, date, environment, assumptions and explicit non-goals.
- Use sanitized fixtures; never publish credentials, caller data, recording URLs or runtime identifiers.
- Show failure modes, stop conditions, rollback and an independent verification step.
- Timestamp prices, regulations and vendor capabilities and prefer primary sources.
- Label lab demonstrations honestly; synthetic setup does not prove production capacity.
Corrections and commercial coverage
Material corrections should update the visible review date and explain the changed conclusion when context requires it. Commercial relationships, supplied access and affiliate links must be disclosed on the affected page. Advertising does not determine technical conclusions or rankings.
Use the contact page to report a reproducible error. Include the public URL, the disputed claim and non-sensitive evidence.