Application Modelling

(1)

Seminar on Model-Based Testing as a Service

Application Modelling

Author:

Antti Heimola

Date:

Dec-4, 2008

Time:

Thu Dec- 4, 2008

(2)

Content

Model based Testing

Case: KENDO

- Testing modelling/automation needs

- Time it takes

(3)

Model based Testing

James Bach’s Blog:

The Unbearable Lightness of Model-Based Testing

Question:

How do you suggest that you apply this technique with a complex

application, something like MS Word for instance.

“

I’m not sure what technique you are referring to. If you are talking about

using state models to describe a system, then it’s interesting that you ask that,

because I asked

Harry Robinson

that same question (it was even about

applying it to Word) after seeing an otherwise fascinating talk about

state-based testing that he gave, years ago. As I recall, he wasn’t ready to answer that

question. But I am.

My answer is: ask Harry

. Seriously, he has actually worked

with model-based testing tools at Microsoft, in the years since I challenged him

on this point.”

(4)

Model based Testing

(5)

Application Modelling:

Case KENDO

GUI modelling tool – flow design tool

Specification tool

Test case generation tool

(6)

(7)

“System Success Factor of Model based Testing” - technical

“SSF = 3x+2y+z” *

System Modelling

Test Execution Control

Test Execution API

System Under Test

Test Support (testability)

Test Services

Communication

Other tools

Test Service API

Communication

x :

y :

z :

PC

Target

Bluetooth, USB, WLAN, IP…

Other tools

Successful model based testing

requires support from test execution

control tool and SUT test services –

“testability built in”

(8)

Test Service example

vw_VerifyText

§

Options

§

vw_VerifyMenu

Sort/Instructions/…/Exit

Test Service must support Capture screen minimum while Test Execution Control takes care of text verification

Capture screen support is NOT enough for verifying the whole menu content – more sophisticated Test Support required

Left soft key is §

Options

§

Options menu contains following items

: Sort, Instructions,…, Exit

Model, i.e. Specification of a system event:

Specification converted to test scripts:

Test scripts driving SUT using provided Test Services:

Question of test automation needs. Many

test tool vendors are happy with “press

button” support

(9)

Levels enabling cross Platform Modelling & Testing

System Under Test

Test Support (testability) Test Services

Communication Test Service API Communication

Bluetooth, USB, WLAN, IP…

System Under Test

Communication

System Under Test

Test Execution Control

Test Execution API

Test Execution Control

Test Execution API

System Modelling

Test Mode

•CPP

•NFT: Performance, Stress, Endurance..

•Probability

•Priority (test data)

+

System Under Test

Communication

System Under Test

Communication

System Under Test

Linux

S60

PC

Etc.

Advanced Features

•Memory Usage

•CPU…

In case Application flow (functionality) is

the same, no modifications needed, the

model can be executed on any platform

supported by Test Execution Control and

Test Services

(10)

History

1. Ross Collard: Test Design: Developing Test Cases from Use Cases, 1999

2. KeyWord based test automation system 2001

3. Mikko Nikkanen

: KENDO I, 2005: Use Case based (test) modelling

4. Mikko Mäkinen

: KENDO II, 2007: Application modelling

5. Productized (internal) version 2008

Idea of integrating Use Cases & KWs

(11)

1999 *

2001 **

2008

*) Ross Collard: Developing test cases from Use Cases, Software Testing&Quality Engineering, July/August 1999 **) Mikko Mäkinen: Model based approach to Software testing 2007, page 28

(12)

• UI level Application Modelling – UI flow Design

• Target: Model all paths, not only some parts of them

• In case a model is too complex, most likely the GUI is too complex to use

• User Roles: Model Designer, Test Designer, Tester

• Clearly separated events:

User Actions, System Responses

• Use of KeyWord based approach was logical: Press a button, Tap, Open Menu

• Managing complex models

• System Model, Application Models, Sub-Models, Use/Test Cases

(13)

KENDO User Roles & Key features

Model Designer, Test Designer, Tester

Model Simulation….

(14)

(15)

Implementing Lean Software Development

Mary and Tom Poppendieck, 2007

- Write executable specifications instead of requirements

- Myth: “The job of testing is to find defects”:

The job of tests is to PREVENT defects, not to find them

(16)

KENDO – time it takes S60 and Maemo

Modeling time

Minutes

Minutes Minutes Minutes

Hours

Application

Model Designer Specification Test Designer Testing (ASTE)