Code Testing Policy
How to interpret code examples
A code example is an illustration of a technique, not a guarantee that it has been tested in every runtime, dependency version, or production environment. Where a page describes a specific test or runtime, that evidence should be stated on that page.
Testing principles
- • Check the relevant language or platform documentation before adopting an example.
- • Validate generated output in the target application and environment.
- • Do not use sample values as credentials or production configuration.
- • Report an incorrect example with its page URL through the contact page.
What this means for readers
This policy does not claim that all examples are covered by an automated test suite. The published material and build checks do not substitute for testing in your application.