All three meeting apps can test your devices before you join. They also share blind spots that matter before an interview, client call or review.

Zoom: zoom.us/test

Open zoom.us/test and click Join. No account, no other participants, no appointment. The test runs as a real meeting with only you in it and walks through three steps.

  1. 1. Speaker. A ringtone plays and Zoom asks whether you heard it. Answering “no” cycles to the next output device.
  2. 2. Microphone. It records a few seconds of you talking and plays it back, checking the audio path rather than only showing a moving level meter.
  3. 3. Camera. Your self-view appears so you can check framing.

Inside a meeting the same checks live under the arrow next to Mute → Audio Settings, and under the arrow next to Stop Video → Video Settings.

Teams: Settings → Devices → Make a test call

In the Teams desktop app, open Settings and more (the three dots), then Settings → Devices, and choose Make a test call under Audio settings. The Test Call Bot asks you to record a short message, plays it back, then shows a summary of how the call went. Microsoft states the recording is deleted immediately after the call and is not retained.

Two things to know about it. The test call is available in the Teams desktop app for Windows and Mac only, so if you join meetings from the browser it is not there. The test call also confirms that Teams completed a call to its Test Call Bot; its summary is not a general network diagnosis.

Google Meet: the green room

On the screen before you join a meeting, click Check your audio and video. Meet lets you choose devices, watch the microphone meter, play a speaker test sound and check the camera preview before joining.

What each one actually covers

What you need Zoom test Teams test call Meet green room
Something to start fromNothing — a public test pageA signed-in Teams desktop appA meeting link to sit in front of
Works in a browserYesNo — desktop app onlyYes
Plays your voice back to youYesYesNo
Says anything about the networkNoConfirms the test call completedNo diagnosis; it shows whether each test worked
Tests the app you are about to useOnly if that app is ZoomOnly if that app is TeamsOnly if that app is Meet

The four things none of them check

  • Your lighting. Every self-view shows you your face, and none of them tell you it is too dark. It is the thing other people notice about your video and you do not, because on your own screen you already know what you look like.
  • Stability over time. A test call lasting twenty seconds cannot distinguish a connection that is fine from one that drops a packet every half minute. Latency and jitter are what break live video, and average speed does not predict them.
  • Whether Windows changed something since last time. Plugging in a headset, connecting a dock or waking from sleep can move your default microphone or speaker. The test tells you the current devices work; it has nothing to compare them against.
  • The other app. A clean Zoom test says nothing about the Teams meeting you are joining in four minutes. Device selection and per-app permissions are kept separately by each application, which is why a camera that works in Windows can still be black in one meeting app.

A test you can run when you do not know which app it is

All three built-in tests check your setup from inside one application and apply only to that application. If you use multiple meeting apps, testing one does not verify the others.

CallReady runs the check outside all of them from the Windows system tray in about ten seconds. It opens a live camera preview and confirms the camera starts, reports the active device with its resolution and frame rate, checks that the microphone receives a signal, and flags input that is too quiet or clipping. It also confirms that an output device exists, measures the light on your face, and measures latency, jitter and approximate throughput. It remembers the devices from your last successful check and warns you when Windows has switched to another one.

It does not replace a test call because nothing outside Teams can confirm that the Teams service is reachable today. It checks whether the machine is ready for the call you are about to join.

Ninety seconds before anything that matters

  1. 1. Close every meeting app you are not about to use, including from the system tray.
  2. 2. Close browser tabs that had camera or microphone access.
  3. 3. Open a preview and confirm you see yourself, in the right camera, lit from the front.
  4. 4. Say a sentence and confirm the level moves — or better, hear it played back.
  5. 5. Then join.

Sources

Frequently asked questions

How do I run a Zoom test without an appointment?
Go to zoom.us/test and click Join. It starts a meeting with only you in it and steps through speaker, microphone and camera. No account is needed.
Why can I not find Make a test call in Teams?
The test call is available in the Teams desktop app for Windows and Mac. If you are on Teams in a browser it is not offered. In the desktop app it sits under Settings and more → Settings → Devices → Audio settings.
Does Microsoft keep the recording from the Teams test call?
No. Microsoft states the recording is deleted immediately after the call and is not retained or used.
Is a test call enough before a job interview?
It confirms your devices work in that one app. It does not check your lighting, does not watch the connection long enough to catch jitter, and does not know whether Windows has switched your microphone since you last succeeded. Those are the failures that show up mid-interview.
My test call sounds fine but people still say I am breaking up.
That is usually the network rather than the microphone, and usually jitter rather than bandwidth. A connection that measures fast can still deliver packets unevenly enough to break live audio, which a short test will not reveal.
Do I have to test in every app I use?
With the built-in tests, effectively yes — each one checks its own app and keeps its own device selection. A check that runs outside the meeting apps covers all of them at once, but cannot confirm any single service is reachable.
Get CallReady