Auto-tools/Projects/Autolog: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 16: Line 16:
|+
|+
| Tasks || Owner || Notes
| Tasks || Owner || Notes
|-
| Investigate TBPL code and determine how much to re-use
| Investigate TBPL code and determine how much to re-use
| Mcote?
| Mcote?
|
|

Revision as of 19:17, 18 February 2011

Goal

The Autolog project seeks to implement a TBPL-like system for viewing test results produced by the a-team's various tools, at least those of which aren't hooked up to TBPL. Such projects potentially include mobile automation, Crossweave, profile manager, etc.

Proposed Implementation

The system will be comprised of both a front-end web UI, and a backend database. The database which will be used is ElasticSearch, the same instance of which we're using for OrangeFactor, since our experience with that seems to indicate that it is fast, reliable, and easy to use.

Communication with the db will be provided by two channels: a REST API, which we can probably build by extending Orange Factor's woo_server.py, and a python library that automation tools can use to post results to the database.

The front-end UI should at least superficially resemble TBPL. Whether or not we will re-use TBPL code is open to question; the current implementation of TBPL is JS-based and is tightly tied to Tinderbox, so it may or may not be a good starting point for a new UI.

Tasks

Tasks Owner Notes
Investigate TBPL code and determine how much to re-use Mcote?