Skip to main content

Going Live QA Checklist

Before going live with Feed.fm in your app. Please perform the following quality assurance checks using the same device (or closest equivalent) as your end users.

API Credentials​

Ensure the correct API keys are used that correspond to your development and production apps. Using the development API key for your production app can cause issues with analytics.

Metadata​

Song metadata should display for 6 seconds when song begins and when a song transitions to the next song

  1. Verify the Song Title is displayed.
  2. Verify the Artist Name is displayed.
  3. Verify the Album Title is displayed.
  4. Verify Powered by Feed.fm or the Feed.fm logo is displayed.

In-App Disclaimer​

The in app disclaimer should be no more than two user clicks from the music experience. Click on Powered by Feed.fm or the the Feed.fm logo and verify the in app disclaimer:
There is no affiliation, connection, association or endorsement of the pro

Testing Stations and Regions​

  1. Select and play all stations.
  2. Verify the stations selected are the correct mapped stations and songs played.
  3. Confirm your app functions properly when no or slow Internet connection is available, or when your user isn't eligible for music playback.

We recommend using a VPN to test ineligibility in different regions. Please contact your Customer Success Manager to We can provide you with test credentials for testing.

Play/Pause​

Users can select play and pause and like/dislike(if applicableaplicable)

  1. Verify the user can select the Play button.
  2. Verify user can select the Pause button.
  3. Verify the user can select the Like button.
  4. Verify user can select the Dislike button.

Volume​

Ensure that tThe station volume is playing at a suitable volume in the following cases:

  1. Verify the default instructor/music volume.
  2. Verify the low/high master volume.

If you’re using faders to independently control the music and instructor volumes:

  1. Verify the low/high music volume (if applicable).
  2. Verify the low/high instructor volume (if applicable).

Logs​

To help diagnose any future issues we recommend:.

  1. Turn on Feed Logging for all clients.
  2. Collect users clientId so it will be possible to identify them.
  3. If possible, have a system to retrieve console logs of a session for a given clientId.
  4. Use player.logEvent (..)to send events to Feed.fm with additional info on a user's actions.You may sendsent events to feed.fm with info on the user actions via a player.logEvent (..). This can be called either before or after an error. You may send what you think is about to be played, message and code, version of client app, timestamp user joining, if user joined live/OD, station is First play, Replay, and anything else of importance.