motodev studio for testing a platform testing based on eclipse

© 2009 by Motorola; made available under the EPL v1.0 | Date March 25th.

MOTODEV Studio for Testing: A Platform Testing based on Eclipse

Christian Kurzke, Eduardo Oliveira, Gustavo de Paula, Leonardo Pedrosa,

and Romulo Filho

2 MOTODEV Studio for Testing: A Platform Testing based on Eclipse | © 2009 by Motorola; made available under the EPL v1.0

MOTODEV Studio

Family of products that targets developers of different Motorola Platforms

Same branding. Similar user experience Integration between different products

Eclipse PlatformEclipse Platform

MOTODEV Studio PlatformMOTODEV Studio Platform

UsersUsers

MOTODEV Studio for Java ME Feature

MOTODEV Studio for Java ME Feature

MOTODEV Studio for WebUIMOTODEV Studio for WebUI

Distribution DevelopersDistribution Developers


MOTODEV Studio Distributed Development

MOTODEV Studio for WebUI Product

Eclipse Platform

StudioPlatform

Platform Team

Eclipse XXXProject

MOTODEVStudio for JavaME

JavaME Team

Eclipse YYYProject

MOTODEVStudio for WebUI

WebUI Team


Eclipse Distributed Development

Web ToolsProject

MylynProject

Eclipse PlatformProject

MTJProject

Eclipse for JavaMEProduct

EPP Team

MTJ Team

Eclipse for JavaEEProductWTP Team

Mylyn Team

Platform Team


Testing Related Problems

Hard to specify Platform vs. Product

Requirements What is mandatory

and what is not?

Requirements PlanningCore

Components

Different test levels Platform specific

Product specific

Integration tests Which team runs

which level of test? When tests are

executed? How to do

regression test?

How to test the platform itself?

How to keep compatility?

GuidelinesPlatform Team

Test PlanStudio for Test


Guidelines

If it is hard to specify, just have a guideline with some samples

Guideline defines What a Studio for X product need to do in order to be integrated with the

Studio platform

Defines what is mandatory and what is optional

Give samples of how to implement each requirements

Simplified format (WiKi)

What is mandatory? Basic definitions (branding related, installer, etc.)

Integration guidelines (how one studio should be integrated with the other) – not in the first version

All the rest of the guideline is optional


Studio Platform Test Plan

PlatformDevelop.

Core Plat.System Test

JavaMEDevelop.

Studio JavaMESystem Test.

ComplianceTests

IntegrationTest

Platform Team

JavaME Team Focus only on the

JavaME features Isolated Test Follow Platform

Guideline

Focus only on the platform Features

Isolated Test

Check if the Studio JavaME followed the guideline

Isolated Test

Verify Studio for JavaME integration with the other Studios


Compliance Tests

Similar to a certification process

Run by the Platform Team

Test cases based on the Platform Guideline

Check only mandatory requirements

Not a stop release Test Just report non-compliant requirements to Studio for X team


Studio for Test

Simulates one Studio for X Developed by a separated team

Based on the guideline

Semi-automated tests

Validate the guideline

Make sure that the compatibility is not broken

Can be used to pre-validate Studio integration Studio for X needs to work ok with Studio for Test


Conclusions

Distributed developed & Testing is possible! This is done everyday in OOS world

The requirements of the final product are hard to specific

The test plan is probably the most complex part

A clear guideline to each distributed team helps to minimize the problem

Automation of the tests of all basic components also minimize the issue

Some kind of certification of each distributed component is also interesting

MOTODEV Studio for Testing: A Platform Testing based on Eclipse | © 2009 by Motorola; made available under the EPL v1.0

Thanks

motodev studio for testing a platform testing based on eclipse

Documents