Differences between revisions 1 and 9 (spanning 8 versions)
⇤ ← Revision 1 as of 2011-05-17 07:50:03 →
Size: 1017
Editor: heb
Comment:
← Revision 9 as of 2011-05-17 11:51:34 → ⇥
Size: 2481
Editor: heb
Comment:
Deletions are marked like this. Additions are marked like this.
Line 9: Line 9:
=== Validate that a video can be played === === Test the validation module ===
Confirm that video streams are validated correctly.

==== Validate that a video can be played ====
Line 14: Line 17:
 1. Insert parameters:{{{
Server: rtmp://<server>:<port>/chaos?sessionID=drp3_91.700_DR-P3_pcm_20060821045601_20060822045502.mp3&objectID=976&includeFiles=true
Stream: mp3:drp3_91.700_DR-P3_pcm_20060821045601_20060822045502.mp3}}}
 1. Success: The media file is played in the browser.

==== Validate that a video is rejected ====
Line 15: Line 25:
  a. Server: rtmp://130.225.24.62:1936/chaos?sessionID=drp3_91.700_DR-P3_pcm_20060821045601_20060822045502.mp3&objectID=976&includeFiles=true   a. Server: rtmp://<server>:<port>/chaos?sessionID=invalid&objectID=976&includeFiles=true
Line 17: Line 27:
 1. Success: The media file is played in the browser.  1. Success: Nothing is played in the browser.

=== Test eventlogging ===
Confirm that events are logged correctly.

==== Test that events are sent to MCM ====
 1. Generate event sequence by doing the following
  a. Start video playback by pressing the Play button
   a. Wait 3 seconds
  a. Pause playback
  a. Resume playback
   a. Wait 4 seconds
  a. Rewind
   a. Wait 6 seconds
  a. Seek to somewhere in the middle
   a. Wait 3 seconds
  a. Pause playback
  a. Seek to somewhere in the middle
  a. Resume playback
   a. Wait 3 seconds
  a. Pause playback
  a. Stop playback
 1. The result in MCM is expected to be (Event, start, stop):
  a. (PLAY, 0, 0)
  a. (PAUSE, 0, 3.000)
  a. (REWIND, 3.000, 7.000)
  a. (PAUSE, 0, 6.000)
  a. (PAUSE, 200.000, 203.000)
  a. (PAUSE, 100.000, 103.000)
  a. (STOP, 0, 0)
 1. Verify that the same result can be found in the db.
 
==== Test that local logging can be turned off ====
 1. Set property {{{StatisticsLoggingLocallyInDB}}} to {{{false}}}.
 1. Generate a few event.
 1. Check that events are logged in MCM
 1. Check that events are missing in local DB.

Integration test - Version 1

The purpose of this test is to validate that an installation of the wowza plugin was successful.

Prerequisites

  1. An MCM session validation server must run. This test assumes that the MCM validation server mock is used. See Setup MCM validation server mock for instructions on how to set the server up.

Integration tests

Test the validation module

Confirm that video streams are validated correctly.

Validate that a video can be played

  1. Start Wowzas SimpleVideoStreaming client:

    1. Linux: file:///usr/local/WowzaMediaServer/examples/SimpleVideoStreaming/client/simplevideostreaming.html.

    2. Mac: file:///Library/WowzaMediaServer/examples/SimpleVideoStreaming/client/simplevideostreaming.html.

    3. Windows: ...

  2. Insert parameters:

    Server: rtmp://<server>:<port>/chaos?sessionID=drp3_91.700_DR-P3_pcm_20060821045601_20060822045502.mp3&objectID=976&includeFiles=true
Stream: mp3:drp3_91.700_DR-P3_pcm_20060821045601_20060822045502.mp3
  3. Success: The media file is played in the browser.

Validate that a video is rejected

  1. Insert parameters:

    1. Server: rtmp://<server>:<port>/chaos?sessionID=invalid&objectID=976&includeFiles=true

    2. Stream: mp3:drp3_91.700_DR-P3_pcm_20060821045601_20060822045502.mp3
  2. Success: Nothing is played in the browser.

Test eventlogging

Confirm that events are logged correctly.

Test that events are sent to MCM

  1. Generate event sequence by doing the following
    1. Start video playback by pressing the Play button
      1. Wait 3 seconds
    2. Pause playback
    3. Resume playback
      1. Wait 4 seconds
    4. Rewind
      1. Wait 6 seconds
    5. Seek to somewhere in the middle
      1. Wait 3 seconds
    6. Pause playback
    7. Seek to somewhere in the middle
    8. Resume playback
      1. Wait 3 seconds
    9. Pause playback
    10. Stop playback
  2. The result in MCM is expected to be (Event, start, stop):
    1. (PLAY, 0, 0)
    2. (PAUSE, 0, 3.000)
    3. (REWIND, 3.000, 7.000)
    4. (PAUSE, 0, 6.000)
    5. (PAUSE, 200.000, 203.000)
    6. (PAUSE, 100.000, 103.000)
    7. (STOP, 0, 0)
  3. Verify that the same result can be found in the db.

Test that local logging can be turned off

  1. Set property StatisticsLoggingLocallyInDB to false.

  2. Generate a few event.
  3. Check that events are logged in MCM
  4. Check that events are missing in local DB.

Integration test - version 1 (last edited 2011-05-17 12:21:20 by heb)