MOTODEV Studio for Testing: A Platform Testing based on Eclipse Christian Kurzke, Eduardo Oliveira, Gustavo de Paula, Leon...
MOTODEV Studio <ul><li>Family of products  that targets developers of different Motorola Platforms </li></ul><ul><li>Same ...
MOTODEV Studio Distributed Development MOTODEV Studio for WebUI Product Eclipse Platform StudioPlatform Platform Team Ecli...
Eclipse Distributed Development Web Tools Project Mylyn Project Eclipse Platform Project MTJ Project EPP Team MTJ Team WTP...
Testing Related Problems <ul><li>Hard to  specify </li></ul><ul><li>Platform  vs.  Product  Requirements </li></ul><ul><li...
Guidelines <ul><li>If it is hard to specify, just have a  guideline  with some samples </li></ul><ul><li>Guideline defines...
Studio Platform Test Plan <ul><li>Focus only on the JavaME features </li></ul><ul><li>Isolated Test </li></ul><ul><li>Foll...
Compliance Tests <ul><li>Similar to a  certification process </li></ul><ul><li>Run by the Platform Team </li></ul><ul><li>...
Studio for Test <ul><li>Simulates one Studio for X </li></ul><ul><ul><li>Developed by a  separated team </li></ul></ul><ul...
Conclusions <ul><li>Distributed developed & Testing is  possible ! This is done everyday in OOS world </li></ul><ul><li>Th...
Thanks
Upcoming SlideShare
Loading in …5
×

MOTODEV Studio for Testing A platform testing based on Eclipse

627 views

Published on

EclipseCon 2009 presentation

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
627
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Hello everyone, I am Wang Feng from Sybase. I will talk about the multi-configuration support for MTJ – the Mobile Tools for Java.
  • MOTODEV Studio for Testing A platform testing based on Eclipse

    1. 1. MOTODEV Studio for Testing: A Platform Testing based on Eclipse Christian Kurzke, Eduardo Oliveira, Gustavo de Paula, Leonardo Pedrosa, and Romulo Filho
    2. 2. MOTODEV Studio <ul><li>Family of products that targets developers of different Motorola Platforms </li></ul><ul><li>Same branding . </li></ul><ul><li>Similar user experience </li></ul><ul><li>Integration between different products </li></ul>Eclipse Platform MOTODEV Studio Platform Users MOTODEV Studio for Java ME Feature Distribution Developers MOTODEV Studio for WebUI
    3. 3. MOTODEV Studio Distributed Development MOTODEV Studio for WebUI Product Eclipse Platform StudioPlatform Platform Team Eclipse XXX Project MOTODEV Studio for JavaME JavaME Team Eclipse YYY Project MOTODEV Studio for WebUI WebUI Team
    4. 4. Eclipse Distributed Development Web Tools Project Mylyn Project Eclipse Platform Project MTJ Project EPP Team MTJ Team WTP Team Mylyn Team Platform Team Eclipse for JavaME Product Eclipse for JavaEE Product
    5. 5. Testing Related Problems <ul><li>Hard to specify </li></ul><ul><li>Platform vs. Product Requirements </li></ul><ul><li>What is mandatory and what is not? </li></ul>Requirements Planning Core Components <ul><li>Different test levels </li></ul><ul><ul><li>Platform specific </li></ul></ul><ul><ul><li>Product specific </li></ul></ul><ul><ul><li>Integration tests </li></ul></ul><ul><li>Which team runs which level of test? </li></ul><ul><li>When tests are executed? </li></ul><ul><li>How to do regression test? </li></ul><ul><li>How to test the platform itself? </li></ul><ul><li>How to keep compatility ? </li></ul>Guidelines Platform Team Test Plan Studio for Test
    6. 6. Guidelines <ul><li>If it is hard to specify, just have a guideline with some samples </li></ul><ul><li>Guideline defines </li></ul><ul><ul><li>What a Studio for X product need to do in order to be integrated with the Studio platform </li></ul></ul><ul><ul><li>Defines what is mandatory and what is optional </li></ul></ul><ul><ul><li>Give samples of how to implement each requirements </li></ul></ul><ul><ul><li>Simplified format (WiKi) </li></ul></ul><ul><li>What is mandatory? </li></ul><ul><ul><li>Basic definitions (branding related, installer, etc.) </li></ul></ul><ul><ul><li>Integration guidelines (how one studio should be integrated with the other) – not in the first version </li></ul></ul><ul><ul><li>All the rest of the guideline is optional </li></ul></ul>
    7. 7. Studio Platform Test Plan <ul><li>Focus only on the JavaME features </li></ul><ul><li>Isolated Test </li></ul><ul><li>Follow Platform Guideline </li></ul>Platform Develop. Core Plat. System Test JavaME Develop. Studio JavaME System Test. Compliance Tests Integration Test Platform Team JavaME Team <ul><li>Focus only on the platform Features </li></ul><ul><li>Isolated Test </li></ul><ul><li>Check if the Studio JavaME followed the guideline </li></ul><ul><li>Isolated Test </li></ul><ul><li>Verify Studio for JavaME integration with the other Studios </li></ul>
    8. 8. Compliance Tests <ul><li>Similar to a certification process </li></ul><ul><li>Run by the Platform Team </li></ul><ul><li>Test cases based on the Platform Guideline </li></ul><ul><li>Check only mandatory requirements </li></ul><ul><li>Not a stop release Test </li></ul><ul><ul><li>Just report non-compliant requirements to Studio for X team </li></ul></ul>
    9. 9. Studio for Test <ul><li>Simulates one Studio for X </li></ul><ul><ul><li>Developed by a separated team </li></ul></ul><ul><ul><li>Based on the guideline </li></ul></ul><ul><ul><li>Semi-automated tests </li></ul></ul><ul><li>Validate the guideline </li></ul><ul><li>Make sure that the compatibility is not broken </li></ul><ul><li>Can be used to pre-validate Studio integration </li></ul><ul><ul><li>Studio for X needs to work ok with Studio for Test </li></ul></ul>
    10. 10. Conclusions <ul><li>Distributed developed & Testing is possible ! This is done everyday in OOS world </li></ul><ul><li>The requirements of the final product are hard to specific </li></ul><ul><li>The test plan is probably the most complex part </li></ul><ul><li>A clear guideline to each distributed team helps to minimize the problem </li></ul><ul><li>Automation of the tests of all basic components also minimize the issue </li></ul><ul><li>Some kind of certification of each distributed component is also interesting </li></ul>
    11. 11. Thanks

    ×