Open Test Lab - Revision history

Cschalle: Add category

2011-10-27T22:50:41Z

Add category

Tim Bird: /* Test Lab Hardware */

2009-12-03T00:57:17Z

‎Test Lab Hardware

Tim Bird: /* Other pages related to the test lab */ de-orphan a hardware page

2009-12-03T00:21:04Z

‎Other pages related to the test lab: de-orphan a hardware page

Tim Bird: de-orphan several pages

2009-12-03T00:17:27Z

de-orphan several pages

Tim Bird: de-orphan links

2009-12-02T22:22:08Z

de-orphan links

Prpplague at 21:49, 24 September 2007

2007-09-24T21:49:29Z

New page

http://tree.celinuxforum.org/CelfPubWiki/OpenTestLab

The purpose of the lab is, at the highest level, the same as the purpose of the forum, which is to help enhance Linux and Linux technologies for use in Consumer Electronics products.

The lab exists to provide testing and quality assurance benefits to the entire Linux community, including CE Linux forum members.

The core of the lab is located in San Jose, but a satellite lab (an extension to the main lab) is planned for Tokyo, and additional lab nodes may be added to the lab as part of a completely distributed lab model.

The lab is available for use by CE Linux Forum members, and will be made available to open source community members as well.

The lab provides resources for a number of different testing activities:

*Interactive board usage via remote access - In this mode, an individual developer reserves a target board in the lab, and interactively compiles the kernel and other software, loads it on the target board, and runs tests on the board. This mode allows a developer to have access to hardware which they don't have on their own desk.
*Automated multi-platform testing - A developer can also request that the same test be performed across multiple platforms. This is useful to see whether a particular feature or fix works on multiple platforms, or to compare performance or functionality results between platforms.
*Nightly regression tests - The test lab will be configured with a set of tests to run at periodic intervals (e.g. nightly), using software updated to latest versions. This will be used to test for regression of features or functionality, and results will be provided to the public. In particular, the results are intended to be useful to the open source community, to notify developers about problems in new versions of Linux software.
*Private test usage - In addition to public use of lab hardware, and publishing of open results, tests from the lab will be made available for private use. That is, a client can use the tests and test infrastructure of the lab to test a board locally. The lab infrastructure should make this very easy. The intent of this is to make the lab useful for internal quality assurance testing, whether for private individuals or large corporations.

← Older revision		Revision as of 22:50, 27 October 2011
Line 47:		Line 47:

	Additional information about the hardware for the lab is kept in the internal wiki for lab administrators.		Additional information about the hardware for the lab is kept in the internal wiki for lab administrators.
		+
		+	[[Category: Open Test Lab]]

@@ Line 43: / Line 43: @@
 ** how to use a USB-to-serial converter for serial console access
 ** web-controlled power control module - http://www.digital-loggers.com/EPC.html
 Additional information about the hardware for the lab is kept in the internal wiki for lab administrators.

← Older revision		Revision as of 00:21, 3 December 2009
Line 30:		Line 30:
	* [[Test Lab Board Suppliers Guide]]		* [[Test Lab Board Suppliers Guide]]
	* [[Test Lab Programs]]		* [[Test Lab Programs]]
		+
		+	== Test Lab Hardware ==
		+	The hardware for the lab is described here. Some of this equipment has been purchased, and some target boards have been delivered already.
		+
		+	Here are some of the individual hardware items that will be used in the lab:
		+
		+	* server - accessible from the outside: See http://testlab.celinuxforum.org/
		+	* firewall
		+	* host/target combinations
		+	* control modules
		+	** [[Target Switch Control From Parallel Port]] - this page has information about how to build your own module to control target switches using the parallel port on a standard PC (the host)
		+	** how to use a USB-to-serial converter for serial console access
		+	** web-controlled power control module - http://www.digital-loggers.com/EPC.html
		+
		+	Additional information about the hardware for the lab is kept in the internal wiki for lab administrators.

← Older revision		Revision as of 00:17, 3 December 2009
Line 24:		Line 24:

	A template for new lab test wiki pages is at: [[Lab Test Template]]		A template for new lab test wiki pages is at: [[Lab Test Template]]
		+
		+	== Other pages related to the test lab ==
		+	* [[Test Lab Architecture]]
		+	* [[Test Farm Project]]
		+	* [[Test Lab Board Suppliers Guide]]
		+	* [[Test Lab Programs]]

@@ Line 1: / Line 1: @@
 http://tree.celinuxforum.org/CelfPubWiki/OpenTestLab
@@ Line 13: / Line 12: @@
 The lab provides resources for a number of different testing activities:
-*Interactive board usage via remote access - In this mode, an individual developer reserves a target board in the lab, and interactively compiles the kernel and other software, loads it on the target board, and runs tests on the board. This mode allows a developer to have access to hardware which they don't have on their own desk.
+* Interactive board usage via remote access - In this mode, an individual developer reserves a target board in the lab, and interactively compiles the kernel and other software, loads it on the target board, and runs tests on the board. This mode allows a developer to have access to hardware which they don't have on their own desk.
-*Automated multi-platform testing - A developer can also request that the same test be performed across multiple platforms. This is useful to see whether a particular feature or fix works on multiple platforms, or to compare performance or functionality results between platforms.
+* Automated multi-platform testing - A developer can also request that the same test be performed across multiple platforms. This is useful to see whether a particular feature or fix works on multiple platforms, or to compare performance or functionality results between platforms.
-*Nightly regression tests - The test lab will be configured with a set of tests to run at periodic intervals (e.g. nightly), using software updated to latest versions. This will be used to test for regression of features or functionality, and results will be provided to the public. In particular, the results are intended to be useful to the open source community, to notify developers about problems in new versions of Linux software.
+* Nightly regression tests - The test lab will be configured with a set of tests to run at periodic intervals (e.g. nightly), using software updated to latest versions. This will be used to test for regression of features or functionality, and results will be provided to the public. In particular, the results are intended to be useful to the open source community, to notify developers about problems in new versions of Linux software.
-*Private test usage - In addition to public use of lab hardware, and publishing of open results, tests from the lab will be made available for private use. That is, a client can use the tests and test infrastructure of the lab to test a board locally. The lab infrastructure should make this very easy. The intent of this is to make the lab useful for internal quality assurance testing, whether for private individuals or large corporations.
+* Private test usage - In addition to public use of lab hardware, and publishing of open results, tests from the lab will be made available for private use. That is, a client can use the tests and test infrastructure of the lab to test a board locally. The lab infrastructure should make this very easy. The intent of this is to make the lab useful for internal quality assurance testing, whether for private individuals or large corporations.