Testing Templates & Grading Rules: What the Tester Sees

The test checklist a tester walks through and the grading rules that combine the picks into a letter aren’t hard-coded. Both live in tenant settings, with platform defaults as the fallback. /settings/core/testing/templates is the editor.

Test checklist templates

Each device category has a test checklist template: the steps the tester runs, the order they run them in, the expected pass criteria for each step. Laptops have battery-health, screen-pixel, keyboard, port-set, BIOS-check, OS-boot. Servers have RAID, RAM-banks, power-supply-redundancy, network-link, BIOS. Mobile phones have FaceID, camera, charging port, speaker.

The templates are tenant-configurable. A tenant whose mix is mostly heavy-grade laptops can customize the laptop checklist to add a stress-test step. A tenant who handles industrial-control hardware can add a category that the platform default doesn’t cover. The platform default applies until the tenant overrides; the override only changes that tenant’s view.

Grading rules

The platform default grading rules: cosmetic 30%, functional 50%, battery 20%, severity-4 floor at D. Tenants can override the weights and the floor logic from the same settings page. The override registers as a tenant_override flag — the page surfaces "you’re using a tenant override, the platform default is X" so the operations lead always knows whether they’re on default or custom rules.

Per-asset version stamp

Each graded asset records the rules version active at grading time. Changing the rules tomorrow doesn’t silently re-grade yesterday’s assets — they retain their original grade and the rules version that produced it. A buyer who disputes a grade can see the exact rules that applied at the time, with the cosmetic/functional/battery weights spelled out.

Why both layers

Different markets have different definitions. A broker who only sells refurbished consumer laptops needs different rules than a recycler who buys for parts. The two-layer system (platform defaults, tenant override) lets the platform ship sensible defaults while letting each tenant tune to their reality.