Professional Documents
Culture Documents
MiLEST Toolbox
Model-in-the-Loop for Embedded System Testing
MiLEST Integration in the W-Model MiLEST Model-based Testing (MBT) is testing in which the
entire test specification is derived in whole or part from
MiLEST applies to the software built into embedded sys- both the requirements and an SUT model that describes
tems. In particular, it refers to the software models from selected functional aspects of the SUT. In this context, the
which systems are built. A model-based approach to func- term entire test specification covers both the abstract test
tional black-box testing is used to provide a test model. scenarios substantiated with concrete sets of test data
This is in marked contrast to current test methods that are and expected SUT outputs. It is organized in a set of test
generally dedicated solutions specialized for specific test- cases.
ing contexts.
Test Development Process
system &
acceptance test The Model-based Development paradigm assumes that
OEM
function design
system
vehicle integration
integration
vehic
icle
the System Under Test (SUT) model is already available
in th
he loop
op
abstract test hardware in the
architectural
specification
component
loop for integration and that the input/output interfaces are clearly defined
design integration
MiLEST
model-based testing and accessible.
MiLEST
model hardware model-based testing
SIMULINK in the loop integration
simulation and model-based design
hardware
software in the loop
design
SIMULINK MiLEST
simulation and model-based design Model-Based Testing
supplier
STEP 5 automatic execution
Besides the analysis of the SUT specification, proper func- The structure of the test system consists of four different
tional, dynamic testing also requires systematic selection levels that can be built systematically. This makes it less
of test stimuli, appropriate test evaluation algorithms, error-prone while also leaving the test engineers plenty of
and obviously an execution or simulation environment. If scope for developing the complete test specification.
the above assumptions hold, a pattern for generation of
a test harness model can be applied on the SUT model as Features
denoted in step I. This is done automatically with a
MiLEST transformation function, giving a concrete frame Systematic, consistent functional test specification
for test specification. Further on, the test engineer refines
the test specification design (step II) using the concept of Signal feature-oriented paradigm
validation function patterns. Structures for test stimuli Graphical test design
and concrete test signals are then generated. This step
(step III) occurs automatically with application of the Test process automation
transformations. The test control design can be added systematic and automatic test data generation
automatically too (step IV). Finally, the tests may be exe-
cuted and test results obtained in the form of verdicts online automatic test evaluation
(step V). At the same time the quality of the test system Model-in-the-Loop test execution
specification produced is also assessed.
Reusable test patterns
Hierarchical Test System Abstract and concrete views
te
st
ev
nisms while also building test specifications systemati- test
alu rbitrat
ure sp
at
n
ec
a
ctio
a ti
fe
cally. In this context, the test system is understood as a
ifi
o n, n
abstra
al
ca
sign
tio
t e s t o r a cle,
hierarchically structured test model also called the test
io
n
MiLEST
design. method
t es
ion
tq
at
ua
lit m
y to
au
ss on
te te
u
q
st alit
e
n
st y m ge ve
ls
ra
te etrics na acti
sig
gy test st re
te
abstraction
Contact
Dr. Justyna Zander-Nowicka Prof. Dr. Ina Schieferdecker
MOTION Competence Center Head of MOTION Competence Center
justyna.zander-nowicka@fokus.fraunhofer.de ina.schieferdecker@fokus.fraunhofer.de