Verification and testing

Source checks, software tests and equipment tests answer different questions.

Source checks#

Articles link to the standards bodies, vendors and runtime documentation used for their claims. A dated source check states what was checked. It does not mean every device implements that feature or that the complete article was retested on that date.

Older review dates remain visible where there has not been a new technical check. A wording edit or website build does not change the source review date.

Software tests#

The code examples include runnable programs, offline demos and automated checks. Network examples are tested against local fixture services where a result is stated. The checks include successful responses and selected failure cases.

A passing parser test does not establish protocol conformance. A successful connection to a local simulator does not establish compatibility with a camera, controller or monitoring receiver.

Equipment tests#

Record the product, firmware, configuration, account permissions, test inputs and expected results. Include failure behaviour, recovery and any effect on other connected systems. Obtain authorisation before sending requests to real equipment.

Product conformance, site acceptance and regulatory compliance require the applicable assessment process. The wiki does not issue those approvals.

Metadata in the repository#

Source files preserve the existing review records. V0 identifies guidance without a technical verification claim. V1 records a source check, V2 adds broader source and static review, and V3 identifies a defined environment result. Read the scope and date alongside the label.

A value of not-executed means the code has not been run under the documented test scope. partially-runtime-validated means only specified cases were executed. Do not treat those labels as a general compatibility promise.

Evidence records for new source checks#

A new checked_on date requires checked_scope and an evidence_record link. The record must identify the source, edition, claim, access date and what remains unverified. The builder validates the link; it cannot establish that the source supports the claim.

Inherited check dates are kept as previous_checked_on with their recorded scope. They do not become fresh verification merely because the website was rebuilt or the source URL responded successfully. A working link does not establish that its source supports a claim.