Difference between revisions of "Test Farm Project"

From eLinux.org
Jump to: navigation, search
(add deprecation warning to this page)
(add link to "Board Farm" page)
 
Line 2: Line 2:
  
  
''NOTE: - this page is deprecated.  It describes a project that is no longer in operation.  The CELF test farm was started in 2007, and ran until approximately 2010.''
+
''NOTE: - this page is deprecated.  It describes a project that is no longer in operation.  The CELF test farm was started in 2007, and ran until approximately 2010.'' For current activities on board farm, please see [[Board Farm]]
  
 
== Description ==
 
== Description ==

Latest revision as of 06:25, 23 October 2017

Table Of Contents:


NOTE: - this page is deprecated. It describes a project that is no longer in operation. The CELF test farm was started in 2007, and ran until approximately 2010. For current activities on board farm, please see Board Farm

Description

This page describes the CELF embedded development board test farm project. The purpose of this project is to provide benefits to open source developers, CE developers and embedded board vendors.

Rationale

This project is important to CELF because it solves a few different problems in the open source community:

  • developer access to hard-to-obtain boards
  • developer access to a variety of boards and processors
  • target board testing by a variety of developers

Resources

Projects

Specifications

See Remote Board Access Spec

Also, we need to document rtest.

Downloads

Nothing right now.

How To Use

The following high-level usage scenarios are envisioned:

  • an open source developer logs in to a host machine and runs tests manually on a specific, individual target board
  • an open source developer submits a patch and compiles it (and tests it) on many different boards
  • CELF runs a large test suite on a periodic basis, and delivers the results to the open source community
  (possible audiences would be kernel arch maintainers, toolchain developers, and target board vendors)

Either of the first two scenarios would be available to a CE vendor engineer (CELF member) acting as an open source developer.

Future Work/Action Items

Here is a list of things that could be worked on for this feature:

- publish the spec.
  - publish the hardware specs for the remote reset switch
- release the existing programs for comment
  - finish the programs enough to perform first compile-time testing
- run a pilot program
  - get a board server set up somewhere
  - get a set of pilot boards
    - Samsung, Renesas, TI (OSK)??
  - ask for volunteers to test the program
    - Erik Andersen, Matt Mackall, Paul Mundt, SZWG
  - get the first test suite
    - Linux Tiny Test Project