%0 Conference Proceedings
%T Using Robustness Testing to Handle Incomplete Verification Results When Combining Verification and Testing Techniques
%+ University of Tübingen
%A Huster, Stefan
%A Ströbele, Jonas
%A Ruf, Jürgen
%A Kropf, Thomas
%A Rosenstiel, Wolfgang
%Z Part 1: Model Based Testing
%< avec comité de lecture
%( Lecture Notes in Computer Science
%B 29th IFIP International Conference on Testing Software and Systems (ICTSS)
%C St. Petersburg, Russia
%Y Nina Yevtushenko
%Y Ana Rosa Cavalli
%Y Hüsnü Yenigün
%I Springer International Publishing
%3 Testing Software and Systems
%V LNCS-10533
%P 54-70
%8 2017-10-09
%D 2017
%R 10.1007/978-3-319-67549-7_4
%K Software verification
%K Robustness testing
%K Test vector generation
%Z Computer Science [cs]
%Z Computer Science [cs]/Networking and Internet Architecture [cs.NI]Conference papers
%X Modular verification and dynamic testing techniques are often combined to validate complex software systems. Formal verification is used to cover all input spaces and program paths. However, due to the high complexity of modern software systems, they might not achieve complete verification results. Dynamic testing techniques can easily be applied to any type of software. Current approaches use them to handle incomplete verification results by validating unverified sections. This way of combining verification and testing ignores the fact that tests can only be used to show the presence of errors, but not their absence. Undiscovered errors pose the risk to trigger further errors in vulnerable code sections. Vulnerable sections are modularly verified, but depend on the guarantees of the tested code. We include robustness testing to analyse the influence of undiscovered errors. The generated robustness tests simulate failed guarantees within the tested code. The triggered response to those simulated errors helps the developer in adding additional error handling code. This makes the system more robust against undiscovered errors and guards it against uncontrolled crashes and unexpected behaviour in case of software failures. In the second part of this paper, we introduce a reference-architecture to generate and apply robustness tests. This architecture has been applied to multiple case studies and helped to identify potential errors yet undiscovered by generated test cases.
%G English
%Z TC 6
%Z WG 6.1
%2 https://inria.hal.science/hal-01678963/document
%2 https://inria.hal.science/hal-01678963/file/449632_1_En_4_Chapter.pdf
%L hal-01678963
%U https://inria.hal.science/hal-01678963
%~ IFIP-LNCS
%~ IFIP
%~ IFIP-TC
%~ IFIP-WG
%~ IFIP-TC6
%~ IFIP-WG6-1
%~ IFIP-ICTSS
%~ IFIP-LNCS-10533