Once upon a time, there was a company called COMPRION, devoted body and soul to testing. One day, we decided to purchase two brand-new 5G RedCap devices—because we urgently needed them for the further development and validation of our 5G RedCap test cases. And hey, according to the manufacturer's specifications, they should have been perfect for the job!

Excited, we unpacked the devices, hooked them up, and started our tests. But soon, we furrowed our brows: The device was acting strangely, the USIM data wasn’t being read correctly, and the radio interface was… silent. Radio silence. Absolute silence.

“Hmm… maybe we missed something?” we thought. So, we double-checked everything. But no—the issue wasn’t on our end. Our first suspicion: a software problem? So off went the log files to the vendor. After some time, we got a response:
“Oh… um… yeah… it seems like the device actually doesn’t support RedCap. Our mistake!”

Wait. What?!

We specifically bought devices with a chipset that we knew supported RedCap! How could this happen? Well, maybe something went wrong during the chipset’s integration into the IoT device. Or maybe the devices worked under certain network settings or mysterious card configurations, somewhere in a far-off galaxy—or a specific country. But one thing was clear: The device didn’t behave according to the specifications.

You could think of it like this: We bought a car, knowing the engine was top-notch. But then it turned out someone had been slacking off during the assembly process. Sure, the car might still roll somehow—but that’s definitely not guaranteed.

And the moral of the story?
You can claim a lot of things—but in the end, it’s only what actually works that matters. Trust is good, testing is better!