Testing for GUI, Embedded Systems, Systems Engineering and Distributed Products.

Eugene Chan (IBM), Ryan Brooks, Roberto Escobar, Yuichi Nakamura, Achim Loerke (BREDEX GmbH), Christian Kurzke (Google Inc.), Gustavo de Paula

Frameworks - Test And Performance · Long - curated
Wednesday, 16:30, 50 minutes | Room 203/204

7
·
8
·
9
·
10
·
11
·
12
·
13
·
14
·
15
·
16
·
17
·
18

A collection of talks on testing in different contexts.

Using models to ease the start-up phase of automated GUI testing

Everybody’s talking about models - and with good reason. Modelling tests (and/or software) can certainly help in the planning phases of a project. By reducing the complexity of a program or a test to the fundamentals, it is easier to get a project up and running and to ensure that design has been taken into account.

This talk looks at some of the benefits of using models in the planning phase for auto-mated GUI testing, the effects that modelling can (or should) have on the test process, and how to avoid the pitfalls associated with modelling.

Topics to be covered include the kinds of model available, how and when to start using them, what design aspects should be a part of the model and how formal a model needs to be.

Participants will gain insight into how they can use the documents available to them to introduce modelling to their test process in a meaningful way.

An Integrated Test Environment for Systems Engineering

The Open System Engineering Test Environment (OTE) is a framework for requirements-based testing in the context of an overall systems engineering approach. OTE has been used commercially to qualify mission software for Boeing’s next generation Apache Attack Helicopter and it has been recently contributed as a component of the Open System Engineering Environment (OSEE) Eclipse project.

Some OTE's features include:

  • An extensible messaging system supporting external I/O such as: Ethernet, Mux, Serial, and wire
  • Tools for the monitoring, manipulation, recording, and playback of message data
  • Support for both soft real-time and simulated approaches
  • Periodic scheduling for the execution of models (simulation components)
  • Support for multiple test fidelity levels including a fully simulated environment, test stations with varying degrees of actual hardware, and production line test stations
  • Remote access to the environment including the ability to monitor and manipulate messages and models
  • Support for the running large test batches on multiple machines.
  • Bidirectional traceability from requirements to tests and tests to test results
  • Historical records including failure disposition, test trends, and test run results
  • Customizable reports and document publishing capabilities
  • OTE supports different types of users who test at the various test fidelity levels. From low-level requirements-based testing to production line tests, OTE help software developers to manufacturing personnel achieve better quality control throughout a product’s life-cycle. We will also touch on the current state of the project and future plans.

    Automatic Unit Testing Toolset for Embedded Systems

    In this short talk, the Eclipse-based C/C++ automatic unit testing toolset for embedded systems is presented. This toolset introduces modern unit testing technology to the conventional development environment of embedded systems, by serving as a wrapper for the "CppUnit framework [1]," originally intended for self-development environments. Two plug-ins, a generator plug-in and a user interface plug-in, and a network server have developed for this toolset. The generator plug-in helps to cross-compile the target code with a unit test library. The generated test is sent to the target system and executes in communication with the user interface plug-in and the "GC (Gathering Control)-Stub" remote service server. This GC-Stub is a small and highly portable program running on embedded systems, and is enhanced from what we developed and demonstrated at the EclipseCON in 2007 and 2008, so as to apply various tools sent from the host and return the result. Thanks to these plug-ins and the stub, users can apply prepared CppUnit test scenarios simply by clicking the buttons. The test result is automatically retrieved from the target and shown as if the test is done locally. We will demonstrate our system can operate C/C++ automatic unit testing to enhance the quality of software running at the embedded systems. We also welcome discussions on test issues. [1] http://www.xprogramming.com/software.htm

    MOTODEV Studio for Testing: A platform testing based on Eclipse

    Motorola has introduced the MOTODEV Studio’s products, distributed environments for developers based on Eclipse IDE. Motorola internal teams, distributed geographically, have created distinct products for Motorola end-users, based on Java, WebUI, Linux and UIQ platforms.

    To make it available, the Motorola has created the MOTODEV Studio Platform, built on top of Eclipse Platform, which is the base of all Motorola internal teams products.

    MOTODEV Studio products are tested and validated by each MOTODEV Studio teams. These developers teams has the responsibilty in the ensurance of the quality of their products. On the MOTODEV Platform side, the quality ensurance requires too much effort. The MOTODEV Platform must be responsible for testing the provided features and for checking the other Studios compliance coding and ui standards.

    To ensure the integrity and quality of these products, developed in a distributed way with standard processes, a lot of test were needs. The tests must be capable to identify if a provided feature in MOTODEV Studio Platform is still working in the different Studio's developed by the different internal Motorola teams.

    To test the MOTODEV Studio Platform, a MOTODEV Studio for Testing was developed with the main goal of ensure the quality of the MOTODEV Studio Platform. This MOTODEV Studio for Testing was built on top of MOTODEV Studio Platform, at the same way of other MOTODEV Studios do, and make it possible the identification of problems in Studios or in the MOTODEV Platform side. This MOTODEV Studio for Testing implements all the features provided by the MOTODEV Platform while the others just implement based on theirs own needs.

    The main objective of the MOTODEV Studio for Testing is to identify if an error is from responsibility of MOTODEV Platform or MOTODEV Studio's and allow MOTODEV Platform developers to validate their code in this Studio. Whenever the MOTODEV Platform is updated, the MOTODEV Studio for Testing must be also updated to be able to validate the changes.

    This talk is targeted for developers interested in distributed software products development based on Eclipse platform and distributed product testing. The talk is focused on the test of a product, built on top of the MOTODEV Platform.

    Eugene Chan is a staff software developer at the IBM Toronto Lab. He started in an Eclipse-based problem determination tool project which later became the Eclipse Hyades tool project. Eugene has been a committer on the Eclipse Test and Performance Tools project (TPTP) since its launch at Eclipse.org in 2002, acting as a committer of the Platform and Trace sub project. Eugene is currently the Project Lead of the TPTP Tracing and Profiling Project and the Chairperson of the TPTP Architecture Group.

    Ryan Brooks is the co-lead of the Open System Engineering Environment (OSEE) project. OSEE had its roots in Boeing's Longbow Apache helicopter program where he worked as an Embedded Software Engineer. He earned a Bachelor of Science in Computer Engineering from Auburn University. Previous conference presentations and papers include:
    " The Cure for Your Disconnected Toolset Headache" - EclipseCon 2008; "A Linux/Java Environment for Testing Real-time Avionics Software" – 2nd Boeing Software Conference, 2007; "Lean Engineering and the Open System Engineering Environment" – 1st Boeing Software Conference, 2006; "Lean Engineering and the Open System Engineering Environment" – JACMET Lean Symposium, 2005; "The Eclipse Platform and the Open System Engineering Environment" – 9th Boeing Technical Excellence Conference, 2005; "A Jini-enabled Active Badge System" - 38th Annual ACM Southeast Conference, 2000.

    Roberto Escobar is a software engineer at Boeing and a committer for Eclipse’s Open System Engineering Environment (OSEE) Technology Project. In addition to his work on OSEE, his past projects include the AH64-D Apache Attack Helicopter and Future Combat System’s War-fighter Machine Interface. He has a Bachelor of Science in Computer Engineering from Georgia Institute of Technology and a Masters in Business Administration from Arizona State University.

    Achim Loerke started software development in 1982 after earning his diploma in electronics. He began working at BREDEX GmbH in 1987 and is now co-owner and director of the company. Beginning in 1995 he successfully utilized Java in several customer projects. He is also the principal architect of GUIdancer, a commercial Eclipse based tool for automated testing of Swing, SWT/RCP and HTML GUIs. Doing consulting and project management for customers gives him ample opportunities to apply his favorite subject of automated software quality assurance and automated testing. In addition he represents his company as an Eclipse Foundation member. Achim is a committer for the Eclipse ORMF technology project.

    Christian Kurzke is the Architect for Motorola's Developer Tool suite, MOTODEV Studio.

    Outside of Motorola, he is the lead of the Eclipse Mobile Tools for Java (MTJ) project and founding member of the Eclipse Mobile Industry Working Group.

    Before Eclipse, Christian has been engaged in various other Open Source initiatives and has contributed to the Open Service Gateway initiative (OSGi) standard and CableLabs specifications.
    He is a frequent speaker at conferences like JavaOne, Embedded Systems conferences and WWW conferences. Christian graduated from the University of Erlangen Germany with the degree of Diplom Informatik (MS CS) and holds an MBA degree from the Santa Clara University.

    Mr. De Paula is a current contributor to the MTJ project. He has a long background with wireless technology and has being working with Java in mobile devices since the first release of MIDP 1.0 in 2000. He has implemented several projects for carriers, such as Vivo and BellSounth and handset manufactures, such as Motorola. Mr. De Paula holds a MSc. in Computer Science and has presented at conferences like JavaOne, EclipseCon and ESE Currently he is a Senior consultant for Wireless Technology at CESAR - Recife Center for Advanced Studies and Systems where he works a software architect of for Java development tools.

    Gold sponsors

    IBM Corporation

    Windriver logo

    JBoss

    Sun Microsystems

    SOPERA

    BLU AGE

    BIRT Exchange by Actuate

    Silver sponsors

    Innovations Software Technology

    Google

    Genuitec

    Instantiations

    itemis

    EclipseSource

    Innovent Solutions

    SAP Business Objects

    Hardware Sponsor

    Cisco

    Lanyard Sponsor

    Intel logo



    report a problem with this page