---
title: Testing Voice AI Means Talking to Yourself in Public
description: Building voice AI means reading test sentences aloud in coffee shops, on trains, and in meetings you forgot to mute. It looks as ridiculous as it sounds.
canonical: https://lukeocodes.dev/testing-voice-ai-public
type: article
locale: en_GB
published: 2026-06-05T00:00:00.000Z
modified: 2026-06-05T00:00:00.000Z
authors:
  - Luke Oliff
section: Voice AI
tags:
  - Voice AI
  - Developer Experience
feed: https://lukeocodes.dev/rss.xml
search: https://lukeocodes.dev/search.json?q={query}
schema:
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": WebSite
        "@id": https://lukeocodes.dev/#website
        url: https://lukeocodes.dev
        name: Luke Oliff
        alternateName: lukeocodes
        inLanguage: en
        publisher:
          "@id": https://lukeocodes.dev/authors/luke#person
        description: Personal blog and writing by Luke Oliff — developer relations, voice AI, developer experience.
        potentialAction:
          - "@type": SearchAction
            target:
              "@type": EntryPoint
              urlTemplate: https://lukeocodes.dev/blog/search?q={search_term_string}
            query-input: required name=search_term_string
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
  - "@context": https://schema.org
    "@graph":
      - "@type": Organization
        "@id": https://ably.com/#organization
        name: Ably
        url: https://ably.com
      - "@type": Person
        "@id": https://lukeocodes.dev/authors/luke#person
        name: Luke Oliff
        url: https://lukeocodes.dev/authors/luke
        description: Staff engineer and Staff Tech Lead for Developer Experience at Ably. Writing about developer relations, AI, and the voice industry, from the UK.
        mainEntityOfPage: https://lukeocodes.dev/authors/luke
        givenName: Luke
        familyName: Oliff
        image: https://lukeocodes.dev/authors/luke.jpg
        jobTitle: Staff Tech Lead, Developer Experience
        worksFor:
          "@id": https://ably.com/#organization
        sameAs:
          - https://www.linkedin.com/in/lukeocodes
          - https://github.com/lukeocodes
          - https://bsky.app/profile/lukeocodes.dev
          - https://x.com/lukeocodes
          - https://hashnode.com/@lukeocodes
          - https://dev.to/lukeocodes
        knowsAbout:
          - Developer Relations
          - Developer Experience
          - Voice AI
          - Text-to-Speech
          - Answer Engine Optimisation
          - Search Engine Optimisation
          - Open Source
          - Developer Tooling
          - API Design
          - Speech-to-Text
          - Voice Agents
          - Community Building
        knowsLanguage:
          - English
        nationality: British
        alumniOf:
          - "@type": Organization
            name: The Open University
      - "@type": BlogPosting
        "@id": https://lukeocodes.dev/testing-voice-ai-public#article
        headline: Testing Voice AI Means Talking to Yourself in Public
        alternativeHeadline: Testing Voice AI Means Talking to Yourself in Public
        description: Building voice AI means reading test sentences aloud in coffee shops, on trains, and in meetings you forgot to mute. It looks as ridiculous as it sounds.
        datePublished: 2026-06-05T00:00:00.000Z
        dateModified: 2026-06-05T00:00:00.000Z
        url: https://lukeocodes.dev/testing-voice-ai-public
        mainEntityOfPage: https://lukeocodes.dev/testing-voice-ai-public
        inLanguage: en
        author:
          - "@id": https://lukeocodes.dev/authors/luke#person
        isPartOf:
          "@id": https://lukeocodes.dev/#website
        keywords: Voice AI, Developer Experience
        articleSection: Voice AI
        about:
          - "@type": Thing
            name: Voice AI
          - "@type": Thing
            name: Developer Experience
        abstract: 'Friday fun: I have said "the cat sat on the mat" more times in the last month than most people hear in a lifetime. Not because I love cats or mats. Because that sentence has every phoneme a speech-to-text model needs to test.'
        speakable:
          "@type": SpeakableSpecification
          cssSelector:
            - .post-tldr
            - h1
        image: https://lukeocodes.dev/og.png?h=Testing+Voice+AI+Means+Talking+to+Yourself+in+Public&d=Building+voice+AI+means+reading+test+sentences+aloud+in+coffee+shops%2C+on+trains%2C+and+in+meetings+you+forgot+to+mute.+It+looks+as+ridiculous+as+it+sounds.&e=Writing
        wordCount: 784
        timeRequired: PT4M
        publisher:
          "@id": https://ably.com/#organization
      - "@type": BreadcrumbList
        itemListElement:
          - "@type": ListItem
            position: 1
            name: Home
            item: https://lukeocodes.dev
          - "@type": ListItem
            position: 2
            name: Writing
            item: https://lukeocodes.dev/blog
          - "@type": ListItem
            position: 3
            name: Testing Voice AI Means Talking to Yourself in Public
            item: https://lukeocodes.dev/testing-voice-ai-public
---

[Luke Oliff.](/)

- [Blog](/blog)
- [CV](/cv)
- [Uses](/uses)
- [User manual](/user-manual)
- [Living with ADHD](/living-and-working-with-adhd)
- [RSS](/rss.xml)

[Luke Oliff · Writing](/blog)

# Testing Voice AI Means Talking to Yourself in Public

Jun 2026 · [Voice AI](/blog/category/voice-ai) · 4 min read · [Luke Oliff](/authors/luke)

Friday fun: I have said "the cat sat on the mat" more times in the last month than most people hear in a lifetime. Not because I love cats or mats. Because that sentence has every phoneme a speech-to-text model needs to test.

This is a side of testing voice AI that the docs skip. You spend half your day talking to yourself. The other half you spend explaining to people who walk in on it.

## Why is a coffee shop the worst place to test speech recognition?

The worst place to test STT is a coffee shop. It is also the most realistic test environment. Background chatter, hissing espresso machines, the blender guy who really wants that frozen drink. Every one of them is noise your model has to ignore.

So you sit there with your laptop, put on headphones, and whisper test sentences into a microphone. "The quick brown fox jumps over the lazy dog" at 30% volume while the person next to you is on a perfectly normal business call. You look unhinged. The model hears you fine. Small victories.

## The escalation ladder

Testing voice AI in semi-public places follows a predictable arc.

Stage one: quiet whispering. You mouth the words and hope the mic picks it up. It doesn't.

Stage two: low volume. You speak at library level. The person two tables over definitely heard you say "please call the doctor" into your laptop. You are not actually calling a doctor.

Stage three: full volume. You forgot that the microphone gain is too low. You are now announcing "BANK ACCOUNT NUMBER 4729" at normal speaking volume in a public space. People are looking. It is fine. Everything is fine.

Stage four: the moment of surrender. You take your laptop to a corner table, face the wall, and accept your role as the weird laptop whisperer.

I have been at stage four for about two weeks now.

## Why it matters

The reason I do this instead of using a prerecorded test file is that microphones matter. A lot. A test file from a studio microphone tells you nothing about how your agent will perform through a 2020 MacBook mic in a room with a refrigerator hum. The only way to know is to sit in that room and talk to the thing.

Deepgram's Python SDK shipped declarative reconnect this week, which means I can drop a WebSocket connection in the middle of a sentence and watch it recover. That is the kind of edge case you cannot test with a recorded file. You have to be there. You have to drop the connection yourself and say "hello? hello? can you still hear me?" into your own product.

## How to test your voice agent in the real world

If you are building a voice agent, test it in the worst environment your users will be in. Not the quietest one. Sit in a coffee shop with mediocre wifi and read test sentences until your model stops mishearing "sixty-six" as "sexty sicks." Record the audio, check what it heard, fix the prompt, repeat.

Your users will be in those environments. You should be too.

And if you see someone in a coffee shop whispering "the cat sat on the mat" into a laptop, do not worry about them. They are doing quality assurance.

## FAQ

### Why do voice AI developers test with specific test sentences?

Standard test sentences like "the quick brown fox jumps over the lazy dog" or "the cat sat on the mat" contain all the phonetic elements a speech model needs to verify its accuracy across different sounds, consonants, and vowel combinations. Using the same sentences across tests makes accuracy comparisons consistent.

### What is the most realistic environment to test a voice agent?

The environment your users will actually be in. For most voice agents that means noisy public spaces with background chatter, music, appliances, and variable microphone quality. Testing only in a quiet room gives you no signal about real-world performance.

### Why not just use prerecorded audio files for testing?

Recorded files cannot simulate microphone variability, room acoustics, breathing artifacts, or the way real people pause, stumble, and restart sentences. A studio recording will pass every test and tell you nothing about how your voice agent performs through a laptop mic in a noisy room.

### What is declarative reconnect in the Deepgram SDK?

A feature added to the Deepgram Python SDK 7.3.0 in June 2026 that lets WebSocket connections automatically recover when a network drop happens, without the application code managing retry logic. It means the SDK handles reconnection transparently so the voice agent stays in conversation even through wifi blips.

[← Newer: Six tools that power production voice agents](/six-tools-production-voice-agents)

[All posts](/blog) →

## Search this site

`GET https://lukeocodes.dev/search.json?q=<words>` returns matching posts as JSON, each with its page URL and its markdown URL. Add `&limit=<1-50>` for more than 10. How it works: [/blog/search](https://lukeocodes.dev/blog/search.md).

```sh
curl "https://lukeocodes.dev/search.json?q=developer+relations"
```

---

© 2026 Luke Oliff. Posts live at the root of this site.

- [GitHub](https://github.com/lukeocodes)
- [LinkedIn](https://www.linkedin.com/in/lukeocodes)
- [X](https://x.com/lukeocodes)
- [Bluesky](https://bsky.app/profile/lukeocodes.dev)
- [Email](mailto:luke@lukeoliff.com)
- [RSS](/rss.xml)

## Cookies

This site sets one analytics cookie, from Google Analytics, and only in a browser that accepts the cookie banner. A client that does not run scripts sets no cookies, so there is nothing to accept or decline here.

[Cookie policy](/cookies)
