Facilities for Testing Control Software Pieter J. Schoenmakers - - PowerPoint PPT Presentation

▶
facilities for testing control software
SMART_READER_LITE
LIVE PREVIEW

Facilities for Testing Control Software Pieter J. Schoenmakers - - PowerPoint PPT Presentation

Facilities for Testing Control Software Pieter J. Schoenmakers <tiggr@ics.ele.tue.nl> Eindhoven University of Technology November 1997 Overview What is control software? What is the problem? The


slide-1
SLIDE 1

Facilities for Testing Control Software

Pieter J. Schoenmakers <tiggr@ics.ele.tue.nl>

Eindhoven University of Technology November 1997

slide-2
SLIDE 2

– 1 – November 1997 Facilities for Testing Control Software

Overview

  • What is control software?
  • What is the problem?
  • The architecture
  • The testing architecture
  • Design for test
  • Implementation
  • Application
  • Conclusion
slide-3
SLIDE 3

– 2 – November 1997 Facilities for Testing Control Software

Control Software

control software hw/sw system codesigned hw / sw environment

control software is

✁

high-level

✁

no stream / data processing

✁

developed independent of codesign process

slide-4
SLIDE 4

– 3 – November 1997 Facilities for Testing Control Software

Problem Statement

How to test control software?

✂

at (sub-) system level

✂

prior to hardware availability

✂

unattended

✂

independent of hardware / availability

Generalizing

✂

how to test software that interacts with hardware

✂

independent of hardware

✂

unattended

✂

convert control software into ‘normal’ software

✂

normal testing methods apply

✂

normal tools can be used

slide-5
SLIDE 5

– 4 – November 1997 Facilities for Testing Control Software

The Architecture

codesigned hw / sw environment control software core hardware abstraction hardware abstraction hardware abstraction

…

slide-6
SLIDE 6

– 5 – November 1997 Facilities for Testing Control Software

The Testing Architecture

test driver simulated environment control software under test core hardware model

… t e s t i n g e x t e n s i

  • n

hardware model hardware model hardware model:

  • simulator / emulator
  • special purpose sw
  • anything
slide-7
SLIDE 7

– 6 – November 1997 Facilities for Testing Control Software

Design for Test

Hardware

✄

test: the design a particular instance

✄

testing facilities: part of design

Software

✄

test: the design

✄

testing facilities: not part of design

slide-8
SLIDE 8

– 7 – November 1997 Facilities for Testing Control Software

Implementation

premise: object oriented programming language mechanism: ability to amend objects’ behavior

☎

modify / add behavior replace / add methods

☎

support complex behavior add instance variables

☎

no recompilation

facilities: driver and framework

☎

test driver

☎

extensible simulated environment

☎

testing extensions framework

slide-9
SLIDE 9

– 8 – November 1997 Facilities for Testing Control Software

Application

proof of concept: elevator control

✆

service s systems of f floors using e elevators

✆

simulated environment

✆

cage movement (constant speed, infinite acceleration)

✆

inhabited by p persons

✆

push buttons

✆
  • bserve an elevator or floor
✆

test execution

✆

scenario generation (no record or playback)

✆
  • utcome: conditions, invariants
slide-10
SLIDE 10

– 9 – November 1997 Facilities for Testing Control Software

Conclusion

method

✝

testing software that normally interacts with hardware

✝

independent of the hardware

✝

usual sw testing methods apply

✝

independent of source availability

✝

testing extensions are not part of the design

models

✝

hardware models

✝

flexible

✝

simple models suffice for high abstraction testing

✝

testing is only as good as the models

✝

models need to be tested as well