FOKUS

1
FOKUS View on MODEL-Based Test Description
Languages (TDLs)

• Alain-G. Vouffo Feudjio

2
Outline

• Motivations Why Model-Based Test Design
• FOKUS View on TDL by Example
• Discussion

3
Why Model-Based Test Description (I)

• Test design at early phase of the product
  lifecycle
• Enhanced reuse of test design.
• Facilitated communication between stakeholders.
• Facilitated integration of testing in MDE process
  by filling the gap between requirements and
  testing.
• Higher quality of test specifications through
  Application and Automated Verification of Test
  Design Guidelines.
• Unified and test execution platform-independent
  test design.
• Facilitated Reuse of legacy test scripts through
  Round-Trip Engineering in Test Automation.
• E.g. Visualization of legacy test scripts for
  reuse.

4
Why Model-Based Test Description (II)

• Requirements traceability.
• Early identification of flaws in system
  specification.
• Integration of test-related activities in the
  overall MDE process.
• Time savings, Costs reduction
• Automated generation of executable test scripts
  through model-to-model (M2M) or model-to-text
  (M2T) transformations from system model to test
  model and backwards.

5
Model-Based Test Design Process
Test Model
Test Architecture Model
Test Objectives Model
System Description
DSMLs
Requirements
Test Suite
TTCN-3
Test Data Model
Test Procedures Model
Executable Testcases or Skeletons
Informal System/Test Specification
Test Behaviour Model
Test Documentation
System Model
(Automated) Test Model Transformation
Model-Based Test Design
Optional
6
The UTML Notation as a TDL

• FOKUS follows a two-way approach to test
  modeling/designing
• A pure UML approach (UTP) based
• A UML-Like approach based on a DSML called UTML
  (Unified Test Modeling Language)
• UTML combines concepts of TTCN-3, UML (TP) and
  SysML into a DSML for designing tests at high
  level of abstraction
• Based on an EMF (eMOF) Meta-Model
• Currently supports 3 representation formats
• Tree Tabular
• Graphical
• Allows a Formalization and exploitation of
  patterns in test design to guide and speed up the
  process

7
Model-Based Test Design ITS DENM Example
8
Model-Based Test Design Test Objective/Purpose
Design
9
Model-Based Test Design Test Architecture Design
10
Model-Based Test Design Test Behaviour Design
Dont worry You will NOT have to enter this as
source code. Its just a label created out of the
provided model elements.
11
Model-Based Test Design Test Behaviour Design
using Activity Diagram
Dont worry You will NOT have to enter this as
source code. Its just a label created out of the
provided model elements.
12
Model-Based Test Design Transformation
13
A Few Remarks

• Models are transformed. Therefore, only
  information contained therein can be transformed
  or exploited
• Models may provide different Levels of detail.
  Obviously, the ability to generate automatically
  executable test cases will depend on the
  completeness of the information provided in the
  modelling
• The test models may be used by model-based test
  generation to apply combinatory algorithms for
  generating a larger number of variants of the
  test case, although those would be functionally
  equivalent (From a conformance testing
  perspective)
• As any matter of taste, obviously the graphical
  diagram elements may be more or less appreciated,
  depending on the organization and the individual,
  but they can be considered as inter-changeable.
  Focus should be laid on the concepts, rather than
  their representation

14
TDL Goals of standardization

• Define a standardized concept space as
• MOF/EMF Metamodel ?
• Other ?
• Define and standardize
• Representation formats?
• Graphical visualization concepts?
• Textual syntax?