Contents 1 0.9 Planning Meeting Agenda (WIP) 1.1 1. Server Side Proposals 1.1.1 Monitoring 1.1.2 Persistence Layer 1.1.3 GUI 1.1.4 Reporting 1.2 2. Worker Side Proposals 1.2.1 Conductor 1.2.2 Testrunner 1.2.3 HW Controllers 1.3 3. Control Files 1.4 4. Project Planning 1.5 5. Open Source Approach 2 Minutes 2.1 Server side 2.2 Worker side 2.3 Project Planning

0.9 Planning Meeting Agenda (WIP)

1. Server Side Proposals

Monitoring

How to satisfy the monitoring needs of the various users.

Persistence Layer

What extent does OTS support persistence layers?

e.g.

• API
• SQLite Database
• mysql, postgresql...
• ORM
• ORM + view
• Distributed database

GUI

Are we providing GUIs?

Reporting

Test result reporting to QA-Reports database. [1]

2. Worker Side Proposals

Conductor

• Python APIs

• Function to replace CL in tasks

• E-P proposals

Testrunner

• testrunner-lite

• Python implementation

• APIs

HW Controllers

• Custom Flasher replacement

• Power Control interface

3. Control Files

• 6Pack tests.xml part of the request

• Control Flow requirements

4. Project Planning

• Timescales

• Version Releases

• Team Work Distribution

5. Open Source Approach

Can we take libraries, frameworks, IP from other projects, similar domains to help us?

e.g.

• SCADA
• Modbus (probably quite a few implementations: python, xml ....)
• PyVisa
• Pythics
• Labview

Minutes

Meeting was arranged on 30th November 2010 in Jyväskylä Quality/QA-tools/Workshops.

Server side

• Distributor/Server
  • User can give test plan as input
  • Test plan is split and delivered to the workers
  • Need for changing reporting to test case level?
  • Now it is done in test package level

• Monitoring
  • Monitor is needed
  • Publisher plugin
  • Statistics, how many test executions are executed, pass/fail %
  • Usage of the worker
  • Percent usage
  • What test cases
  • Queue list
  • Error rate
    • Flashing errors
    • Failures overall
• GUI
  • We have to deliver simple GUIs
  • Monitoring
  • Logging (0.8 has simple logging monitor)
  • No GUI needed at this point for making requests, BOSS will handle

• Reporting
  • Support for qa-reports.meego.com
  • http://bugs.meego.com/show_bug.cgi?id=9353

Worker side

• Conductor
  • Changing conductor to be a library
    • CLI interface stays, but Worker won't use the CLI interface
  • Introducing new layer for device control
    • Replacing current customflasher
    • All device traffic goes via this layer
  • Getting rid of testrunner-lite CLI
    • Makes logging and debuggin easier

Project Planning

• Creating feature items to bugzilla
• Releasing minor releases
  • When necessary, example bug fixes
• Quality
  • Code reviewing
  • System testing for releases
    • Using virtual environment and clean target
  • CI for checking OTS commits
    • Code coverages
    • Pylint
    • Common development repository
    • Checking and running that repository