Documentation

Support

Vivox Core SDK

Vivox Core SDK

Smoke test

What to look for when smoke testing Vivox.
Read time 1 minuteLast updated 20 hours ago

When a user has voice enabled, UI elements indicate channel join state and what options (for example, mute, push-to-talk) are active and usable. Otherwise, UI elements aren't active or indicate that a user isn't in a channel.
  • UI elements
    • User is connected to a Vivox voice network but is not in a channel or call.
    • User is in a channel or call, and they see a personal speaking indication or for another person.
    • Microphone is active or inactive (muted).
    • Push-to-talk is active or inactive.
  • UI function controls
    • Selecting a channel to enter gets the user to the expected channel.
    • If mute for me is implemented, check for persistence by restarting the game.
    • Entering or leaving a channel works.
    • Choosing a different capture (microphone) or render (loudspeaker) device correctly updates the UI.
  • Logging checkpoints
    • Vivox voice network connection, login, and session creation.
    • Channel activity: for example, speaking indications.
    • Capture device or render device changes: for example, volume or changing devices.
    • Vivox connectivity is monitored. For example, an error is thrown when voice unexpectedly disconnects or logouts.