{"ddc":["040"],"page":"17-18","file":[{"success":1,"file_id":"1532","file_name":"186-SEsubmission8.pdf","access_level":"closed","content_type":"application/pdf","relation":"main_file","date_updated":"2018-03-21T12:32:11Z","date_created":"2018-03-21T12:32:11Z","creator":"florida","file_size":55775}],"project":[{"name":"SFB 901","_id":"1"},{"name":"SFB 901 - Subprojekt B4","_id":"12"},{"name":"SFB 901 - Project Area B","_id":"3"}],"has_accepted_license":"1","abstract":[{"lang":"eng","text":"Software verification is an established method to ensure software safety. Nevertheless, verification still often fails, either because it consumes too much resources, e.g., time or memory, or the technique is not mature enough to verify the property. Often then discarding the partial verification, the validation process proceeds with techniques like testing.To enable standard testing to profit from previous, partial verification, we use a summary of the verification effort to simplify the program for subsequent testing. Our techniques use this summary to construct a residual program which only contains program paths with unproven assertions. Afterwards, the residual program can be used with standard testing tools.Our first experiments show that testing profits from the partial verification.The test effort is reduced and combined verification and testing is faster than a complete verification."}],"file_date_updated":"2018-03-21T12:32:11Z","date_created":"2017-10-17T12:41:28Z","editor":[{"first_name":"Uwe Zdun","last_name":"Jens Knoop","full_name":"Jens Knoop, Uwe Zdun"}],"language":[{"iso":"eng"}],"series_title":"Lecture Notes in Informatics","date_updated":"2022-01-06T06:53:43Z","type":"conference","publication":"Software Engineering 2016","year":"2016","status":"public","author":[{"first_name":"Mike","last_name":"Czech","full_name":"Czech, Mike"},{"full_name":"Jakobs, Marie-Christine","last_name":"Jakobs","first_name":"Marie-Christine"},{"first_name":"Heike","id":"573","last_name":"Wehrheim","full_name":"Wehrheim, Heike"}],"_id":"186","title":"Just test what you cannot verify!","department":[{"_id":"77"}],"user_id":"477","citation":{"short":"M. Czech, M.-C. Jakobs, H. Wehrheim, in: U.Z. Jens Knoop (Ed.), Software Engineering 2016, 2016, pp. 17–18.","apa":"Czech, M., Jakobs, M.-C., &#38; Wehrheim, H. (2016). Just test what you cannot verify! In U. Z. Jens Knoop (Ed.), <i>Software Engineering 2016</i> (pp. 17–18).","chicago":"Czech, Mike, Marie-Christine Jakobs, and Heike Wehrheim. “Just Test What You Cannot Verify!” In <i>Software Engineering 2016</i>, edited by Uwe Zdun Jens Knoop, 17–18. Lecture Notes in Informatics, 2016.","mla":"Czech, Mike, et al. “Just Test What You Cannot Verify!” <i>Software Engineering 2016</i>, edited by Uwe Zdun Jens Knoop, 2016, pp. 17–18.","bibtex":"@inproceedings{Czech_Jakobs_Wehrheim_2016, series={Lecture Notes in Informatics}, title={Just test what you cannot verify!}, booktitle={Software Engineering 2016}, author={Czech, Mike and Jakobs, Marie-Christine and Wehrheim, Heike}, editor={Jens Knoop, Uwe ZdunEditor}, year={2016}, pages={17–18}, collection={Lecture Notes in Informatics} }","ama":"Czech M, Jakobs M-C, Wehrheim H. Just test what you cannot verify! In: Jens Knoop UZ, ed. <i>Software Engineering 2016</i>. Lecture Notes in Informatics. ; 2016:17-18.","ieee":"M. Czech, M.-C. Jakobs, and H. Wehrheim, “Just test what you cannot verify!,” in <i>Software Engineering 2016</i>, 2016, pp. 17–18."}}