Overview

As a lead developer I coordinated the technical development of a stand alone testing software. It is especially useful for the automotive industry. The tool itself is primary glue code for many third party libraries, which was developed in an enterprise environment.

Due to an NDA I can’t tell too much about it, but you can visit the official product page for further details.

Features

Intuitive User Interface • Model Based • Systematic Test Case Specification • Systematic Test Case Generation • Automated Test Case Execution • Test Objectives • Linking with DOORS (specification tool) • Find Test Coverage Gaps • Search Function • etc.

Technologies & Methodologies

• Project Management: Jira • Confluence
• Languages: UML • Java • XML • XSD • CSS • Scripting Languages
• Models and Methodologies: Statecharts
• Libraries & Frameworks: Eclipse RCP • EMF • OSGI • GMF • Many Third Party Libraries
• Automated Builds: PDE, Ant, Custom Scripts
• Automated Testing: JUnit, QF-Test
• Continious Integration: Jenkins, SVN
• IDE: Eclipse

Team & other Stakeholders

• Product Owner: corperate colleague located in another city
• Technical Lead: myself
• Development & Deployment: myself + 6 developers in 2 cities
• Testing: 3 Testers in 3 cities and 2 countries
• Marketing: 2 corperate colleagues located in another city
• Third party software developers: 5 organizaton with differently close contact
• Customer: 1 Customer with direct influence on the product features.

The post State Based Testing Software appeared first on Oliver Stadie - Portfolio.

Idea

Testing Graphical User Interfaces (GUI) is done very differently in commercial and academic environments. In commercial environments GUIs are tested with the simple and convenient Capture and Replay method. Academically developed GUI test methods use powerful but inconvenient model based approaches on the other hand.

My approach combines both methods to a convenient but powerful GUI testing method. The basic idea is the following:

1. The user executes example sequences on a GUI
2. A Model of the GUI is Generated
3. Test Sequences on the Model are Automatically generated
4. The Test Sequences are automatically executed on the GUI

The GUI Models stay compact and clear because they use hierarchies and orthogonality.

A systematic combinatorial approach generates the Test Sequences. This keeps the sequences complete but lean.

Features

Convenient but Powerful GUI-Testing • Capture-&-Replay Approach • Model Based • Systematic Test Sequence Generation • Automatic Model Generation • User Friendly GUI Models • Complete but Compact Test-Sequences • Test Arbitrary GUIs

Prototype

As part of my final thesis I also developed a prototype. The prototype is a Plugin for the commercial testing tool TESTONA. You can see it in action here:

[Archived: embedded content unavailable]

Technologies & Methodologies

Context

This was a self organized project as an employee in the Berner & Mattner enterprise.

To realize this project I worked together with many other teams. I modified and integrated parts of their work into my GUI Testing Tool.

Details

I released a scientific paper   as part of this project. I also released the final thesis  and the final presentation  (in german).

[Archived: embedded content unavailable]

The post GUI Testing – A Concept and Tool to Test any Graphical User Interface appeared first on Oliver Stadie - Portfolio.