Statistical validation

Trust the result.
Inspect the evidence.

Plotwright checks its numerical output against published examples, independent library implementations and closed-form identities. Each check names its dataset, expected value and tolerance.

How a result earns trust

Three independent anchors, used where they fit.

A passing test is useful only when its reference is meaningfully independent of the implementation under test.

01 / PUBLISHED

Reproduce reported results

Canonical datasets from textbooks, papers and R documentation are run end to end and compared with the reported statistics.

02 / INDEPENDENT

Cross-check another implementation

Results are compared with established numerical libraries such as SciPy, statsmodels, lifelines and scikit-learn when an equivalent implementation exists.

03 / IDENTITIES

Pin the underlying mathematics

Closed-form calculations and non-circular identities catch cases where two software implementations could share the same mistake.

Worked benchmarks

Recognizable datasets and transparent stress tests.

This readable subset combines published examples with explicitly labeled synthetic stress tests. Each entry identifies its source, expected result and numerical anchor.

What this does—and does not—prove

Validation is analysis-specific.

A benchmark supports the exact statistic, options and numerical tolerance it exercises. It is not a blanket guarantee that every method is appropriate for every dataset. Researchers remain responsible for study design, assumptions, exclusions and interpretation.

When a result differs from its reference, the automated suite fails. New statistical features are expected to add an independent oracle before they ship.

Test it with data whose answer you already know.

Start with a published example or one of your lab's verified projects. Inspect the Results sheet, assumptions and generated methods text before adopting a workflow.