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 architecture The testing architecture Design for test Implementation Application Conclusion Facilities for Testing Control Software November 1997 – 1 –
✁ ✁ ✁ Control Software hw/sw system codesigned control software hw / sw environment control software is high-level no stream / data processing developed independent of codesign process Facilities for Testing Control Software November 1997 – 2 –
✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂ ✂ 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 Facilities for Testing Control Software November 1997 – 3 –
The Architecture control software core hardware abstraction codesigned hardware abstraction hw / sw … environment hardware abstraction Facilities for Testing Control Software November 1997 – 4 –
The Testing Architecture control software under test test driver core hardware n o simulated environment model i s n e t x hardware e model g n i t … s e t hardware model: • simulator / emulator hardware • special purpose sw model • anything Facilities for Testing Control Software November 1997 – 5 –
✄ ✄ ✄ ✄ 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 Facilities for Testing Control Software November 1997 – 6 –
☎ ☎ ☎ ☎ ☎ ☎ 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 Facilities for Testing Control Software November 1997 – 7 –
✆ ✆ ✆ ✆ ✆ ✆ ✆ ✆ ✆ 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 observe an elevator or floor test execution scenario generation (no record or playback) outcome: conditions, invariants Facilities for Testing Control Software November 1997 – 8 –
✝ ✝ ✝ ✝ ✝ ✝ ✝ ✝ ✝ ✝ 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 Facilities for Testing Control Software November 1997 – 9 –
Recommend
More recommend