Contents 1 Design Review 0.8 1.1 Wiki 1.2 Code 1.3 Known Issues 1.3.1 Input Plugin 1.3.2 ReportPlugin 1.3.3 Plugins 1.3.4 Configuration 1.3.5 TestrunId 1.3.6 Persistence Layer 1.3.7 Components 1.4 Testing 1.5 0.9 Targets 1.6 AOB / Matter Arising

Design Review 0.8

Agenda proposal for the 0.8 Design Review week beginning 18 October.

Wiki

Walk through

Code

Walk through

Known Issues

Input Plugin

The InputPlugin is Maemo specific and probably 'deprecatable' can we extend the top level API and lose it before 0.8?

ReportPlugin

Is this part of 0.8 Release?

• If so review APIs. Nokia internal reporting / meego qa-reports.
• If not how do we organise the hooks for existing users

Plugins

• Loading
• Defining documenting extension points
• Strategy for emerging requirements

Configuration

• Location / Naming
• Nesting issues
• ConfigParser deficiencies (Nesting)
• Python files risks
• Other options yaml / ConfigObj / ZCML / XML etc....
• Aiming for consistency

TestrunId

• Incrementing / UUID ID
• Relationship with Persistence Layer(s)
• Passed parameters / 'Global' (e.g. http://pypi.python.org/pypi/Contextual)

Persistence Layer

• Internal OTS persistence layer requirements
• Technology (Django / SQLAlchemy / CouchDB etc)

Components

• Worker naming issues
• Degree of Formalisation (Distributor for example)
• Code base organisation (Degree of influence of recommended deployment model on code layout)

Testing

Currently there are

• Unittests
• ComponentTests

What are the System Tests? How to Automate?

0.9 Targets

Start adding items...

AOB / Matter Arising

...