Using the RDM Test UI - Revision history

Peternewman: /* Reporting Bugs */ Update link to Github

2014-02-28T17:46:10Z

‎Reporting Bugs: Update link to Github

2012-11-11T03:19:50Z

2012-11-11T03:11:37Z

2012-11-11T02:28:39Z

2012-11-10T03:51:54Z

‎Starting the Test Server

2012-11-10T03:49:33Z

‎RDM Responder Tests

2012-10-01T05:12:26Z

2012-10-01T05:06:22Z

2012-09-27T16:51:28Z

2012-09-27T16:47:14Z

@@ Line 74: / Line 74: @@
 == Reporting Bugs ==
-If an error occurs while running the tests or collecting RDM responder information a dialog box will be displayed. Clicking on the 'Report Bug' button will open a new window and allow you to submit a bug report. The bug tracking system is hosted on Google Code, so you'll need to sign in with a Google account.
+If an error occurs while running the tests or collecting RDM responder information a dialog box will be displayed. Clicking on the 'Report Bug' button will open a new window and allow you to submit a bug report. The bug tracking system is hosted on Github, so you'll need to sign in with a Github account.
-All other bugs can be reported at http://code.google.com/p/open-lighting/issues/entry
+All other bugs can be reported at https://github.com/OpenLightingProject/ola/issues
 [[Image:RDM-tests-error-dialog.png|center|thumb]]

@@ Line 28: / Line 28: @@
 This allows you to select the tests to run. You can either add tests individually or select <tt>Add all</tt>. After running the one round of tests the list of failed tests will appear in the second box.
 === Results Page ===
-After clicking the <tt>Run Tests</tt>
+After clicking the <tt>Run Tests</tt> you'll be presented with the test results page. Read the [[RDM_Test_Output|Guide to interpreting the test output]] for an explanation of the logs.
 === Saving the Logs ===
-The logs can be saved for offline analysis.
+The logs can be saved for offline analysis by selecting the <tt>Download Results</tt> button on the results page. You can apply category and result filters to the test logs before saving them.
 == RDM Responder Publisher ==

@@ Line 1: / Line 1: @@
 This guide explains how to run the RDM Responder Tests using the Web UI, and also how to use the RDM Responder Publisher to list your products on the http://rdm.openlighting.org site. The screen shots in this guide may be slightly different to what you see as the software is constantly evolving.
 <div style="border: 1px solid #ff0000; background-color: #ffccff; padding: 3px">
 <b>Warning</b>: The tests send SET messages to the broadcast UIDs. This means that they will change the start address, device label etc. of all devices connected to the controller. Think twice about running this on your production lighting rig.
 </div>
 === Procedure ===

@@ Line 1: / Line 1: @@
 == RDM Responder Tests ==
@@ Line 27: / Line 29: @@
 === Procedure ===
-Under the 'RDM Responder Publisher' tab, select the universe to use.
+Under the 'RDM Responder Publisher' tab, select the universe to use and click <tt>Collect Responder Information</tt>.
 == Reporting Bugs ==

← Older revision		Revision as of 03:51, 10 November 2012
Line 1:		Line 1:
−	~~== Starting the Test Server ==~~
−
−	~~To start the test server, from the command line type:~~
−
−	~~<pre>~~
−	~~rdm_test_server.py~~
−	~~</pre>~~
−
−	~~If you don't have olad running you'll see an error like the following:~~
−
−	~~<pre>~~
−	~~Checking olad status~~
−	~~Error creating connection with olad. Is it running?~~
−	~~</pre>~~
−
	== RDM Responder Tests ==		== RDM Responder Tests ==

← Older revision		Revision as of 05:06, 1 October 2012
Line 1:		Line 1:
	TODO(simon, renzo): fill this in,		TODO(simon, renzo): fill this in,
		+
		+	== Starting the Test Server ==
		+
		+	To start the test server, from the command line type:
		+
		+	<pre>
		+	rdm_test_server.py
		+	</pre>
		+
		+	If you don't have olad running you'll see an error like the following:
		+
		+	<pre>
		+	Checking olad status
		+	Error creating connection with olad. Is it running?
		+	</pre>

	== RDM Responder Tests ==		== RDM Responder Tests ==

← Older revision		Revision as of 16:51, 27 September 2012
Line 30:		Line 30:
	== Reporting Bugs ==		== Reporting Bugs ==

−	If an error occurs while running the tests or collecting RDM responder information a dialog box will be displayed.	+	If an error occurs while running the tests or collecting RDM responder information a dialog box will be displayed. Clicking on the 'Report Bug' button will open a new window and allow you to submit a bug report. The bug tracking system is hosted on Google Code, so you'll need to sign in with a Google account.
		+
		+	All other bugs can be reported at http://code.google.com/p/open-lighting/issues/entry
		+
		+	[[Image:RDM-tests-error-dialog.png\|center\|thumb]]

← Older revision		Revision as of 16:47, 27 September 2012
Line 1:		Line 1:
	TODO(simon, renzo): fill this in,		TODO(simon, renzo): fill this in,
		+
		+	== RDM Responder Tests ==
		+
		+	=== Procedure ===
		+
		+
		+	=== Saving the Logs ===
		+
		+	The logs can be saved for offline analysis.
		+
		+	== RDM Responder Publisher ==
		+
		+	The RDM Responder Publisher can be used to collect information about a device (using RDM) and then publish that information to the http://rdm.openlighting.org site. This allows manufacturers to quickly list their responders on the site.
		+
		+	The following information is collected:
		+	* Device Model ID
		+	* Manufacturer ID
		+	* Product Category
		+	* Personalities (label, index & DMX slot count)
		+	* Sensors
		+	* Software Version Label
		+	* Supported Parameters (IDs only)
		+
		+	=== Procedure ===
		+
		+	Under the 'RDM Responder Publisher' tab, select the universe to use.
		+
		+
		+	== Reporting Bugs ==
		+
		+	If an error occurs while running the tests or collecting RDM responder information a dialog box will be displayed.