Software test introduction
Introduction to module, unit and integration testing of embedded software
Unit (or module) tests form the first test stage in the V-model. They are a proven method for detecting software errors. In this seminar, topics related to these types of tests are explained (code coverage, classification tree method, traceability of test case requirements). The integration test, the next level in the V-model, will also be discussed.
The seminar enables participants to decide whether unit or integration tests are useful for their project or not.
Frank Büchner, Dipl.-Inform., Principal Engineer Software Quality at Hitex.
- 08:30 am: Registration of participants
- 09:00: start of seminar
- 17:15 clock: end
Common technical terms
(Software) unit test, (software) module test, integration test, component test, system test, regression test, mutation test, fault injection test, back-to-back test, robustness test. Test oracle, fuzzing. Black box / white box testing, static / dynamic testing, functional / non-functional testing.
Test case specification methods from the black box point of view
Requirements based, equivalence class method, limits, experience based.
White Box Tests (Static Analysis)
Coding rules, data and control flow anomalies, metrics (McCabe).
Dimensions of code coverage
What dimensions are called in standards such as IEC 61508 or ISO 26262? Definition of dimensions and their relation to each other; Statement coverage; Branch coverage; Condition coverage including the modified condition / decision coverage (MC / DC: modified condition / decision coverage); Benefits and shortcomings of a code coverage measurement.
Introduction to the unit test
What is a unit? How does the unit test work in principle? To what do you need stub functions? Which mistakes can be found, which not? A simple example is tested with the unit test tool TESSY: definition of test cases; Test execution; Evaluation of test results; Measurement of code coverage; Generate a test report.
Classification Tree Method
Introduction to the test case specification technique using the classification tree method (not just for the purpose of unit testing); Proposal for the procedure with the help of TESSY and this technique; Demonstration of the tool integration.
Further unit tests
Handling of called functions (stub functions). Special features of unit tests on hardware.
Introduction to the temporal component test with TESSY.
Traceability of requirements for test cases with TESSY.
Open questions; Support, training and advice; Discussion, reference to further information.
490, - € per participant including meals. Free participation on the following day (day of practice TESSY) is included.
Please note our early bird and save 190 €!
The seminar price will be credited within 6 months of the seminar if you buy a license.
Basic knowledge of the C programming language. Test knowledge is not required. The participants do not need a computer.
If you need a hotel in Karlsruhe, you can orientate yourself here: Hotelliste.pdf