TestManager

Introduction

TestManager is a comprehensive software application developed specifically for testing consumer electronics (CE), broadcast and digital TV services. With TestManager tests can be scaled from a single device to many banks of equipment using any combination and number of RedRat3s and irNetBoxes. The main function of TestManager is to support the automated and interactive control of CE equipment. Automated control takes places via scripts designed for the output of sequences of infrared remote control commands. Interactive control uses on-screen virtual remotes or physical handsets to route commands to selected CE devices.

Download

TestManager V4.70.zip

Documentation

The TestManager Documentation can be found by clicking here.

Change History & Code Snippets

  • Application changes and bug fixes can be viewed here
  • TestManager Python Code Scripts can be viewed here

The TestManager Main Screen

The TestManager Main Screen

 

Scripting

  • Test scripts can be imported, stored and edited within the system. They can be directly edited, or can be uploaded via an on-screen or a physical remote control. TestManager can be used to execute multiple scripts simultaneously and ensures that there is no interference or conflict.
  • The TM Script Language supports set-top box (STB) selection, output or control instructions, time delays and loops. It is adequate for many scripting tasks, but if complex script operations are needed then Python can be used.
  • To create scripts, along with a specially designed built-in editor, TestManager supports the use of external editors and has script capture and recording features via remote control output.
  • TestManager also supports script logging to aid the tracking of IR signal sequences in the event of errors.

TM-ScriptEditor Image

The TestManager Script Editor

Interactive STB Control

testremote image

Example of an On Screen Remote Control

  • When first using TestManager in a test facility, an on-screen remote control can help to validate system set-up, and can also be used to quickly test remote control signal output sequences. Clicking on the remote buttons will cause output of the associated remote control signal to selected STBs.
  • Any combination of STBs can be interactively controlled with on-screen remote controls.
  • A graphical representation of the STB positions can be created to help quickly and intuitively select the STBs to control.

Zoning

  • It can be useful in many situations to split a test facility into different zones, enabling control operations to be targeted at a particular zone. This is useful in situations where some operations fail on a few STBs and so they need more detailed testing, or where different tests are run on different banks of STBs.

Macros

  • A sequence of IR signals can be defined that causes some discrete operation to happen on a STB. This is useful for operations that require multiple signals such as changing channel.

Named Operations

  • Operations can be defined at a functional level rather than simply as a list of remote control signals. This is because for the same operation, different sequences of IR signals may be required for different STBs. For example, different STBs deployed within a test lab may not use the same engineering channel number. A named operation could be configured such that its output to a set of STBs will cause them all to perform the same operation, for example, to switch all STBs to a single channel reference.

Multiuser Access

  • All application data is stored in a relational database that facilitates multi-user access. A user can create and validate a script at their desk in preparation for use at the testing facility.

Test Manager Architecture Fig1

Figure showing TestManager architecture (multi-user mode)

This site uses cookies. Find out more about this site’s cookies.