Review and Testing Methodology
A tutorial can be reviewed without being compiled or run on hardware. These checks establish different things. Follow the specific board, core, library and module assumptions on each page.
What each check means
| Check | Evidence and limits |
|---|---|
| Documentation review | Compare code, pin assignments and electrical assumptions with the cited platform or manufacturer references. This does not establish that a particular clone module matches those references. |
| Automated content checks | Compare YAML with generated output; check local links, assets, metadata and preserved URLs. Passing checks does not establish compilation or circuit operation. |
| Browser checks | Inspect representative viewport sizes and themes, keyboard controls, code copying and overflow. Desktop browser simulation is not physical-device testing or proof that an embedded video plays. |
| Sketch compilation | A recorded compiler result should identify the sketch revision, board profile, core/library versions and result. Code inspection is not compilation, and compilation alone does not verify wiring. |
| Physical hardware testing | A record should identify the actual board/module, power arrangement, procedure, observed results and limits. Expected readings and a reader checklist are not measured results. |
What is currently recorded
Recent revision reports record documentation review, source/output and link checks, and focused Chromium layout checks. Their reports explicitly state when compilation, hardware and playback testing were not performed. Internal reports are retained with the editorial records rather than served as website downloads.
There is no published per-example bench-test record covering the whole catalog. A successful site build is a website generation check. Do not infer that an older sketch was compiled or a circuit physically tested when its page supplies no such evidence. A review date or editorial attribution is not a test certificate.
Board, module and power assumptions
Many examples target a classic ESP32-WROOM DevKit and Arduino-ESP32 3.x, but camera boards and other ESP32 families have different pin restrictions. GPIO numbers are not physical header positions. Check the page's exact board profile, module pin labels, supply requirements and GPIO logic limits.
Breakouts may differ in power regulation, pull-ups and signal voltage. Motors, servos, displays and relays may need separate supplies and suitable interfaces. Keep beginner load examples at low voltage; these tutorials do not establish mains safety, medical suitability, production reliability or unattended operation.
Expected results and reader checks
Expected-output sections explain what to look for; they do not document measurements unless explicitly identified as recorded observations. Thresholds and sensor readings depend on the module and environment. Before changing wiring, disconnect all power. If observations differ, use the tutorial's troubleshooting steps and report the exact board, versions and symptoms.
