Joshua Kiff
All notes

February 11, 2026

What BBA certification taught me about test rigor

  • Q-Bot
  • Testing
  • Certification

Most engineering testing I'd done before running BBA (British Board of Agrément) certification on Q-Bot's underfloor insulation system was testing I designed, against pass criteria I set, reviewed by people who mostly trusted my judgment. Certification testing is a completely different discipline, and it changed how I think about what "tested" means everywhere else I work, robots included.

Someone else's pass criteria, not yours

The first thing that's different: you don't get to define what "good enough" means. BBA testing evaluates the system against externally defined criteria for thermal performance, moisture behaviour, and fire performance: criteria that exist independent of what the engineering team believes is sufficient. That sounds obvious written down, but it changes how you approach the system in practice. You stop asking "does this meet the bar I think is reasonable" and start asking "does this meet the bar that's actually written down, measured the way it's actually measured." Those are not always the same question, and the gap between them is where a lot of test rigor actually lives.

Audited means someone else can reproduce your result

The second thing: certification testing has to be reproducible and auditable by someone who wasn't in the room. Internal testing can get away with "trust me, I ran it and it passed" if the team culture allows it. Certification testing can't, every test has to be documented well enough that an external assessor can look at the method, the conditions, and the result, and agree that the result actually follows from the method. That forced a level of documentation discipline into the testing process that, honestly, our internal-only testing hadn't consistently had before.

Where this shows up back on the robot

The habit that stuck with me: for any system going into the field (and it doesn't matter whether "the field" is a certification lab or a customer's home) I now ask two questions before I call something tested. First, whose bar is this being measured against, and is it written down somewhere independent of my own judgment? Second, if someone else picked up my test results with no other context, could they reproduce the conclusion I reached?

Most internal engineering testing fails at least one of those two questions, and it's usually fine, not everything needs certification-grade rigor. But knowing the difference, and being able to tell which situations actually need the harder standard, is the thing BBA testing taught me that no amount of internal-only testing would have.