1. 1 if you use this format with a picture in the vertical- stripe format, then adjust the RH edge of the title bar to be just L of the stripe. Test Automation – How far should it go? Ian Gilchrist, IPL

2. 2 if you use this format with a picture in the vertical- stripe format, then adjust the RH edge of the title bar to be just L of the stripe. WeW 20 minutes 15 minutes 10 minutes Contents 1.Context and Introduction 2.C++ Example (‘Reverse String’) with script generation, coverage analysis, wrapping 3.C example (‘Reactor’) with table-driven testing, coverage optimisation, robustness testing

3. 3 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ Context C and C++ software Unit and Integration tests ‘High integrity’ systems Up to and including ‘safety-critical’

4. 4 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ The Back Story Personal history I entered the software industry in 1983 as a programmer working mainly in Assembler code Testing then consisted of ‘suck and see’ By 1985 we were using test facilities based on use of emulator, but requiring much manual set up, and interpretation of results from hex output dump of memory. Not pleasant to do! Not repeatable!

5. 5 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ System Requirements Architectural Design Unit Design Detailed Design Code Software Development Lifecycle System Test Acceptance Test Unit Test Unit Test Integration Test Integration Test Source code Analysis Code Does code do what it should? Is code tested sufficiently? Code Coverage requirements Dynamic testing proof

6. 6 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ Why Unit Test? Regulated Industries (avionics, medical, etc) Mandated or highly recommended Structural code coverage Variation by SIL (System Integrity Level) Business-critical Making a profit! Protecting reputation Avoidance of litigation

7. 7 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ Unit/Integration Test - Technical Challenges Test harness creation Finding time to create reusable test harnesses to test all functionality Control of interfaces Making it simple to test object interactions with the rest of the system Flexibility of Black-Box/White-box and OO techniques Having a full tool-kit to test efficiently Selection/Generation of test data for different purpose Functional tests – does code do what it should? Robustness tests – does code survive large data sets? Baseline tests – we know code’ works’ but want a baseline against which to test changes Code coverage Confidence that tests cover the important code Evidence generated is sufficient to meet standards

8. 8 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ 8 Test Harness Creation Test driver harness for units Structured auto-repeatable test cases Checking of Outputs Results production Automation can do this: Parse of project code Generate structured test script case per function/ method parameters, call order, global data, returns test case independence Incorporate checks according to variable type Positive and negative checking of global data Results production

9. 9 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ 9 Control of Interfaces Isolation of units from system Order of calls Different behavior on calls Checking/modifying parameters Simulate Intercept Automation can do this Knowledge of calls made Automated generation of Stubs to simulate calls Wrappers to intercept calls Programmable instances for Stubs and Wrappers Checks on parameters based on types

10. 10 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ Stub for External Object Source Code External Object A function/method in test script with programmable instances Replaces call to external software, firmware or hardware Check Parameters Check Call Sequences Choose Return Parameter value(s) Stub is a dummy function replacing interface to the External Object Stubs

11. 11 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ 11 Wrapper for External Object BEFORE Wrapper AFTER Wrapper Source Code External Object Modify Out Parameters Check Out Parameters Check Call sequences Modify In Parameters and Return Check In Parameters and Return Wrapping A function/method in test script with programmable instances using Before-After or Before-Replace wrapper pairs Intercepts call to external software, firmware or hardware

12. 12 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ 12 Set + Set + Check Private Public Test Driver Data Checks White (clear) Box Testing Call private methods/static functions Set/check private/static data Control of internal calls Automation can do this: Automated accessibility instrumentation Call private methods and static functions Set/check data which is private, in unnamed namespaces and declared static Wrapping calls internal to compilation unit Wrapping OS library calls

13. 13 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ 13 Black Box Testing Large data input sets Checking large output sets Robustness tests Automation can do this: Table-driven test generation Multiple values per parameter Ranges of values Functions calculating values Combinatorial effect calculator Checks on call sequences and returns Robustness rule sets for data types Public Test Driver Data Checks

14. 14 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ 14 Object Oriented Code Test case re-use aligned with code Support for Templates Support for Inheritance Automation can do this: Parallel hierarchy of code and test case re-use C++ template instantiation and testing C++ inheritance and factory method testing Object oriented code coverage

15. 15 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ 15 Integrated Code Coverage Set coverage target in tests Diagnostics over stages / test runs Sensible coverage metrics Coverage redundancy Automation can do this: Coverage Rule Sets Powerful drill-down views, filters and reports Coverage Metrics Entry- Point Coverage Statement Coverage Decision Coverage Call-return Coverage Condition Coverage (including MC/DC) Test case coverage optimization

16. 16 Normal visible chars of IPL Title Font, to ensure that font embedding works: \zxcvbnm,./asdfghjkl;’#qwertyuiop[]`1234567890-=|ZXCVBNM<>?ASDFGHJKL:@~QWERTYUIOP{}¬!”£$%^&*()_+ Large Legacy Code Base Automatic generation of unit tests Reducing reliance on system regression tests Identifying testability issues Automation can do this Automatic generation of passing C unit test baseline Automatic regression suite of makefiles Knowing testability limitations in code Dynamically unreachable code Crash scenarios Data uninitialised or function static Implicit function declarations Compiler type truncation

17. 17 if you use this format with a picture in the vertical- stripe format, then adjust the RH edge of the title bar to be just L of the stripe. C++ Example – ‘Reverse String’ C Example – ‘Reactor’ C Example – ‘Airborne’  End of Introduction

18. 18 if you use this format with a picture in the vertical- stripe format, then adjust the RH edge of the title bar to be just L of the stripe. If you have any questions, please email: Ian.gilchrist@ipl.com THANK YOU FOR ATTENDING!  End of Presentation