Personal tools
The Open Lighting Project has moved!

We've launched our new site at www.openlighting.org. This wiki will remain and be updated with more technical information.

Difference between revisions of "RDM Responder Testing"

From wiki.openlighting.org

Jump to: navigation, search
Line 13: Line 13:
 
== Test Coverage ==
 
== Test Coverage ==
  
As of 6th March 2011 the following PIDs in E1.20 aren't tested:
+
As of 27th March 2011 the following PIDs in E1.20 aren't tested:
  
 
* DISC_UNIQUE_BRANCH
 
* DISC_UNIQUE_BRANCH
Line 23: Line 23:
 
* SUB_DEVICE_STATUS_REPORT_THRESHOLD
 
* SUB_DEVICE_STATUS_REPORT_THRESHOLD
 
* RESET_DEVICE
 
* RESET_DEVICE
* CAPTURE_PRESET
 
* PRESET_PLAYBACK
 
  
 
== Test States ==
 
== Test States ==

Revision as of 14:58, 27 March 2011

As part of the Open Lighting Project a suite of tests for RDM responders has been developed. This enables manufacturers to check how well a RDM device conforms to the E1.20 specification. The tests cases are written in Python, and use the Open Lighting Architecture to communicate with devices.

Useful Links:

Test Categories

Tests are grouped according to the sections in the RDM Categories/Parameter ID Defines table in the E1.20 document. There are some extra categories for specific behavior like error conditions and sub device handling.

Test Coverage

As of 27th March 2011 the following PIDs in E1.20 aren't tested:

  • DISC_UNIQUE_BRANCH
  • DISC_MUTE
  • DISC_UN_MUTE
  • STATUS_MESSAGES
  • STATUS_ID_DESCRIPTION
  • CLEAR_STATUS_ID
  • SUB_DEVICE_STATUS_REPORT_THRESHOLD
  • RESET_DEVICE

Test States

There are four possible result states for a test:

Passed
The responder replied with the expected result
Failed
The responder failed to reply, or replied with an un-expected result
Not Run
This test wasn't run because the responder doesn't support the required functionality or a previous test failed.
Broken
An internal error occurred, this indicates a programming error or an error with the test rig.

Log Messages

Warnings
Warnings indicate behavior that doesn't match the standard, but is unlikely to cause usability issues. Warnings are printed in the summary section of the test output.
Advisory Messages
Advisory messages indicate issues that are not covered by the standard but are likely to cause problems i.e a sensor temperature out side of the stated scale range.