Test Working Group

From Symbian Developer Community

Copy editing required
This article has not yet been copy edited

The following is the description and activities of the Test Working Group (TWG)

1 Background
2 Aim
3 Mandate
4 Scope
5 Stakeholders
6 Structure
7 Membership
8 Timeline & Execution
9 Termination
10 Activities, Progress, and Actions
11 Tests & Testing
12 Actions
13 Meeting history
14 How to contact us?
15 Useful links
16 Test WG Blog
- 16.1 History of blogs around the TWG and testing

Background

The TWG was put in place to address specific needs raised by the Release Council to address the need to demonstrate and improve platform quality.

(As a reference point, general guidelines for WGs can be found here: WG guidelines)

Aim

This is a topic that has been raised in the SF Release Council and clearly is of great interest to anyone adopting Symbian Releases to create devices, adaptations, applications or services.

The aim of the TWG is to drive improvements in the quality of Symbian releases via testing and to focus test efforts as early in the cycle as possible.

The TWG will provide a roadmap which sets out the key stages in delivering a test strategy for the SF which will then become business as usual as part of the release of versions of the platform. Any 'low-hanging fruit' also needs to be taken advantage of to reap any short-term gains for PF quality.

Mandate

The TWG is sponsored by the Release Council (RC). It will engage with all councils as necessary for the completion of the tasks outlined above but will continue to report and be guided primarily by the RC unless the RC agrees to pass sponsorship of the WG over to another council.

Scope

The scope of the TWG is defined by the test approach set out and agreed with the RC.

A Roadmap for the key activities (work packages) that need to be undertaken has also been set out and reviewed with the TWG.

Stakeholders

Device Manufacturers
Operators
Professional Services Companies and related development organisations
Silicon Vendors

Structure

The working group is chaired by Mark Skrebels , Senior Release Manager & RC Chair, Symbian Foundation. The chair shall be impartial and shall have no voting rights.

The remaining structure shall include representation from the member companies represented on the RC and other development organisations with particular knowledge and skills in test and integration as identified by the TWG. To remain efficient and functional, the working group should keep the number of members as small as needed to achieve the aims of the roadmap and these should be spread across the stakeholder groups listed above.

Membership

The members of the TWG are:

Janne Kolari (JK) - Digia, Finland
Tom Whitson (TW) – Docomo/Accenture, UK
Chandra Narayanasamy (CN) - Fujitsu/Cell, UK
Andrew Cooper (AC) - Nokia, UK
Mikael Christersson (MC) - SEMC, Japan [until May 2010]
Pierre Lablond (PL) - STE, France
Fred Maurel (FM) - TI, USA
Jim Clarke (JC) - Symbian, UK
Mark Skrebels (MS) - Symbian, UK (TWG Chair)
Arnaud Lenoir (AL) - Symbian, UK
Mike Kinghan (MK) - Symbian, UK
Fred Blesser (FB) - Symbian, UK

Contacts list: TWG_Contacts

It is expected that members of the group should be able to volunteer around 10-15% of their time to investigate requirements, write up findings and attend working group calls.

Timeline & Execution

27th Aug 2009 - Test WG proposal floated by RC and approved. Membership open for nominations from RC member companies.
30th Oct 2009 - Working Group membership quorum obtained and presented to the RC. Approved.
12th Nov 2009 - Kick-off TWG meeting held. Scope & mandate agreed. Test approach presented for approval. Monthly meeting logistics agreed.
15th Dec 2009 - Test approach approval from all TWG members.
14th Jan 2010 - Report and review of TWG approach and progress at RC f2f in Tokyo.
23rd Apr 2010 - TWG f2f workshop
18-19th May 2010 - TWG report to RC

Planned:

8-9th Sep 2010 - Report and review of TWG progress and way forward at RC f2f Paris

The Roadmap also sets out a timeline of activities to be handled by the TWG.

Termination

The RC as mandating council is responsible for oversight of the TWG itself and when it is satisfied that the WG has achieved the goals set out for it, it will wind up the WG.

The Roadmap will be one factor in determining when the TWG should be wound up and the activities become business-as-usual.

Activities, Progress, and Actions

You can find out what the Test Working Group has been doing, what the current activities are, open actions and the minutes of all the meetings in the sections that follow.