Table of Contents
NumSharp verification lab

Unit Tests & Oracle Dashboard

A correctness inventory with unlike units kept separate: reflected unit tests and unit-test classes, committed NumPy 2.4.2 Oracle test cases, specialized flags/layout/format cases, execution gates, and live interoperability suites.

Committed generated inventory NumPy — Schema — Reflected net8.0 assemblies
Unit tests
—

One reflected method declaration; not an executed result

Unit test classes
—

Grouped ownership surface across the reflected assemblies

Oracle test cases
—

Corpus plus specialized flags, layout, and NPY/NPZ cases

Oracle test classes
—

Classes that run committed Oracle cases and harness checks

Correctness evidence

Legend & How To Read

Unit test
One reflected unit-test method. DataRow and DynamicData metadata is retained, but the dashboard does not invent or headline an execution count.
Oracle test case
One committed input/expected-result case: operands, dtype, shape, layout, parameters, result kind, bytes, or verbatim error. Two BLAS host-pin records are metadata and are explicitly excluded.
Not a pass rate
This is a deterministic inventory and evidence-strength view. Runtime pass/fail belongs to dotnet test; exclusions and open bugs are shown directly rather than counted as passes.

Unit test inventory

Unit tests remain summarized by execution policy and capability group; they are intentionally kept out of the Oracle explorer.

Oracle explorer

Browse every Oracle operation by test cases, files, recorded layout labels, dtypes, parameters, result kinds, and explicit errors.

Status bands

Default run: ordinary unit-test execution Platform gated: conditional runner Manual gated: explicit or high-memory Known bug gate: intentionally excluded Ignored: no runtime execution

Unit Test Execution Policy

Unit-test methods by runner policy; these are inventory counts, not pass/fail results

Unit Test Groups

Source-folder suites deduplicated into broad capability groups; rows show unit tests and classes

Dtype Coverage

Non-exclusive Oracle test case↔dtype links; mixed-dtype cases can contribute to several dtypes

Specialized Oracle Tests

Oracle test cases outside the common operation/index corpus schema

Oracle Evidence Explorer

Oracle operations and their committed test cases; unit tests stay in the aggregate inventory above

Loading correctness evidence...

Coverage Review Queue

Factual evidence counts first; applicability-aware expansion techniques second

    Full Reports

    Generated data and the human-maintained oracle ledgers

    Edit this page