Tested Before You See It

When a security company offers personal safety to its customers, every release we ship lands in their name. A bug is not our problem alone. It is a phone call to our partner, from their customer.

That is why everything we release is tested before you see it, and every change to the code gets an extra, detailed review. Here is how.

Every release, tested

Tess, our AI test and support specialist, tests every release and every ticket on a test environment before it reaches you. She works through the platform and the app the way a user would. She checks that what was fixed is really fixed, and that nothing else broke.

When she finds a problem, she writes it up with the steps to reproduce it and the screenshots, so our developers can fix it fast. One of our own people tests along and reads every ticket before it goes to the developers.

Tess does not replace our own testing. She comes on top of it. And because every test now follows the same standard, every ticket our developers get has the same quality: clear steps, screenshots, what was expected and what happened. That makes their work faster and more pleasant.

Every change, checked in detail

Frits, our AI code reviewer, checks every change to the code, down to the last detail. He looks for mistakes, risks and code that does not follow our own rules, and adds his findings to the merge request as extra information for our lead developer. Frits approves nothing himself. He advises; our lead developer reviews every change and decides.

Help pages that follow the product

A release is only finished when the help pages match it. David, who looks after our wiki and customer documentation, keeps every page up to date when a feature changes. He asks Tess to verify instructions and details on the test environment, and Art to make the right visuals. For our team this is a huge improvement: it saves a lot of work, and our wiki is always current. So the page your team looks up shows what they see on screen.

What it means for your customers

• Fewer surprises after a release.
• Release notes and help pages that match the product.
• Faster fixes, because every problem arrives with the steps to reproduce it.

Testing never replaces our people. It gives them more to work with. Every decision about a release is still made by a person.

Want to know more about who does what? Meet our AI team.

Jarno Heijting, founder of Cuebly