Firebolt® Implementations Test Suite

    Firebolt® Implementations Test Suite


    Article summary

    Note: Playback centric calls are optional.

    #

    Test Case

    Steps

    Expected Results

    Notes

    1

    Launch the Firebolt® Application

    1. Launch app

    2. Observe app starts loading on device UI

    3. Observe app transition to in-app UI/UX

    • parameters.initialization is called when the app launches

    • metrics.ready is called when app transitions from loading screen to in-app UI/UX

    2

    Fatal and non-fatal errors

    1. Launch app

    2. Trigger an error

    • metrics.error is called passing clear parameters and tagged as

      • visible= true if impacting UX

      • visible=false if not impacting UX

    3

    Go into ‘Inactive’ state during stable app UI

    1. Launch app

    2. Let app settles to stable UI

    3. Press Home button on remote

    • App to go away from foreground and device displays platform homepage

    • inactive state

    • Inactive state currently only supported on Xumo TV (formerly XClass TV) and to be expanded to other device in the future

    4

    Go into 'Inactive' state during active playback

    1. Launch app

    2. Let app settle to a stable UI

    3. Playback some content

    4. While playback is in progress, press Home button on remote

    5. Press Home button on remote

    • Observe app goes away from foreground and device displays platform homepage

    • Playback stopped and audio not heard while app is in the background.

    5

    Memory load during startup

    1. Launch app

    2. Start Memory capture

    3. Stop Memory capture after a few mins

    • Memory load is well under 390Mb threshold during stable operation.

    6

    Memory load during playback

    1. Launch app

    2. Stream some content

    3. Start memory capture

    4. Monitor memory load for an extended period of time (i.e. 10-30 minutes)

    5. Stop memory capture

    • Memory load remains under 390Mb during playback.

    7

    Memory load going into 'Inactive' mode from stable UI

    1. Launch app

    2. Let app settle to a stable UI

    3. Press Home button on remote

    4. Start memory capture

    5. Monitor memory usage for a few minutes

    6. Stop memory capture

    • Memory load reduced to ~200Mb.

    8

    Memory load going into 'Inactive' mode from active playback

    1. Launch app

    2. Let app settles to stable UI

    3. Playback some content

    4. While playback is in progress, press Home button on remote

    5. Start memory capture

    6. Monitor memory usage for a few mins

    7. Stop memory capture

    • Memory load reduced to ~200Mb.

    9

    Returning to foreground from inactive mode

    1. After putting app into inactive mode, launch app again

    • App to come to foreground quickly without reloading

    Lifecycle Management

    How to check memory consumption in RWI

    1. Click on "Timelines" tab

    2. Click "Start recording" red button on the top left corner

    3. Click "Entire recording" on the top

    4. Observe memory breakdown


    Was this article helpful?

    What's Next