Testing and requirements, connected, for hardware teams
Every test. Every rig. Every requirement.
Tensol unifies test data from every bench and ties it to the requirements it verifies. Checks run automatically; a pass still waits for a human signature — because that signature is what a review actually accepts.
The verification matrix — watch REQ-PWR-014 clear its limit check as a run lands, then stop and wait for an approver.
Built by founders & operators from
1 day
per failed run
A test fails Friday. Monday is spent digging through logs on three rig PCs to find when it started.
3 formats
before you can start
NI on one bench, UEI DAQ on another, .csv from a third — every debug starts with format archaeology.
1 week
before every gate
The week before every design review: rebuilding the “which requirements did we actually verify” spreadsheet by hand.
Any hardware in. Every requirement tied to the run that proves it.
- 01
Any hardware, any format
Whatever your benches already write —
.mf4,.tdms, ROS bags,.csv, ULog — or live CAN. Nothing to convert, no rig-side changes. - 02
Requirements matched to traces
Import from ReqIF, CSV, Jama, or DOORS. Each requirement points at the test case, the run, and the exact channel that verifies it.
- 03
Signed proof, kept current
Every run re-checks the limits. A failure stands on its own; a pass queues for sign-off, and the approver's name travels with the evidence. Change a requirement and the affected sign-offs flag stale.
Find the moment it broke
One scrubber over every channel from a run — telemetry, decoded CAN, console, video — aligned to the same clock. Sources like .mf4, .tdms and live CAN line up without you converting anything.
Know what a change breaks
Put two builds on the same channel and the deviation is shaded for you, with the software hash, rig, and operator that differed. The question you actually ask — what changed since the last time this passed?
Ask questions across every run you’ve ever done
Query conditions across rigs and months, not one file at a time: bus_voltage < 9 during phase:startup. Results come back as runs you can open, each with its rig, build, and verdict.
bus_voltage < 9 during phase:startup5 runs · 2 rigs · 3 months