Revision as of 14:38, 2 December 2010 (view source) Tgalvin (Talk | contribs) (→Index) ← Older edit		Revision as of 09:48, 3 December 2010 (view source) Tgalvin (Talk | contribs) (→How to get going...) Newer edit →
Line 96:		Line 96:
	* [[Quality/QA-tools/OTS/Flashing | Flashing]]		* [[Quality/QA-tools/OTS/Flashing | Flashing]]
		+
		+	* [[Quality/QA-tools/OTS/Contributions | Contributions]]
	== Argot ==		== Argot ==

---

Revision as of 09:48, 3 December 2010

Contents 1 OTS Index 1.1 Introduction 1.1.1 What it does 1.1.2 Why it does it 1.1.3 How it does it 1.1.4 Installing 1.2 Index 1.2.1 Architecture 1.2.2 APIs 1.2.3 System Wide Concerns 1.3 How to get going... 1.4 Argot 1.5 Standards and Conventions 1.6 Project Planning 1.7 PEP

OTS Index

Welcome to the Open Test System (OTS) Wiki Index.

The User Documentation applies to the 0.1 release.

The Developer Documentation track the 0.8 branch (currently under development - see the Project Planning section below).

Introduction

OTS is the Open Test Service for testing software systems on evolving hardware architectures.

It was born out of the test framework incrementally developed for use on Maemo project and is in use 24/7 by Nokia typically running about 3500 test runs per week

What it does

OTS has the following primary functions:

• Distribution
• Load balancing
• Remote command running
• Hardware control
• Data Acquisition
• Data Analysis

OTS offers the following services:

• Fully Open Source
• Web server
• Extensible Architecture
• Interoperability

Why it does it

Quite simply: to increase efficiency and quality of on-device software testing.

How it does it

The System Overview gives an outline of how OTS works

Installing

Follow the installation instructions

Index

Architecture

• Overview

• Components

• Plugins

• DataFlow

• Behaviour

APIs

• Server

• Distributor

• Results

• Worker

System Wide Concerns

• Testrun Routing

• Ports and Protocols

• Configuration

• Timeouts

• Optimising Throughput

• Watching OTS

How to get going...

• User Documentation

• Development Guidelines

• Developer Documentation

• Setting up Nose tests

• Creating a Publisher

• Making the transition from 0.1 to 0.8

• Flashing

• Contributions

Argot

• Glossary

Standards and Conventions

• Packages

• Error Codes

Project Planning

• Roadmap

• DevelopmentStatus

• Meetings

• ReleaseChecklist

• Release Practices

OTS releases are done when a new release makes sense from OTS point of view. There are no scheduled releases.

PEP

• MimeTypes

• Naming