{"id":608,"date":"2019-09-29T10:18:49","date_gmt":"2019-09-29T10:18:49","guid":{"rendered":"https:\/\/megamart2-ecsel.eu\/?p=608"},"modified":"2019-09-29T10:18:49","modified_gmt":"2019-09-29T10:18:49","slug":"integrationdistiller-automating-integration-testing-object-oriented-applications","status":"publish","type":"post","link":"https:\/\/megamart2-ecsel.eu\/integrationdistiller-automating-integration-testing-object-oriented-applications\/","title":{"rendered":"IntegrationDistiller: Automating Integration Analysis and Testing of Object-Oriented Applications"},"content":{"rendered":"

Introduction to IntegrationDistiller, a new automated solution to help in the testing of component integration scenarios, by Mehrdad Saadatmand.<\/a> The paper has been published at the IEEE International Conference on Industrial Technology, ICIT 2019<\/a><\/p>\n

Software systems typically consist of various interacting components and units. While these components can be tested and shown to work correctly in isolation, when integrated and start interacting with each other, they may fail to produce the desired behaviors and results.<\/p>\n

Integration testing plays an important role in revealing issues in interactions among cooperating components<\/strong>. Identifying different interaction scenarios, however, is not a trivial task when performing integration testing. On the other hand, most of the integration testing solutions proposed in the literature are manual which hinders their scalability and applicability when it comes to large industrial systems.<\/p>\n

In this paper<\/a>, we introduce IntegrationDistiller as an automated solution and tool to identify integration scenarios and generate test cases (in the form of method call sequences) for .NET applications. It works by analyzing the code and automatically identifying class couplings, interacting methods, as well as invocation points. Moreover, the tool also helps and supports testers in identifying timing issues at integration level by automatic code instrumentation at invocation points.<\/p>\n

More specifically, this paper and the tool that we introduce contribute with the following points:<\/p>\n

    \n
  1. an automated solution to analyze classes, their dependencies and interactions, and generate test cases exercising those interactions,<\/li>\n
  2. automated analysis of object-oriented source code and determining invocation points,<\/li>\n
  3. automatic code instrumentation at invocation points to estimate timing properties and enable testing for timing issues at integration level.<\/li>\n<\/ol>\n

    The main novelty of the work thus lies in providing a fully automated approach for integration analysis and generation of integration level test cases based on automatic data-flow analysis.<\/p>\n

    The code analysis engine of IntegrationDistiller is built and automated using .NET compiler platform, known as Roslyn<\/a>. Hence, this work is the first in utilizing Roslyn features for automatic integration analysis and integration test case generation<\/strong>. This work has been done as part of our collaboration with ABB Industrial Automation Control Technologies<\/a> (IACT) in V\u00e4ster\u00e5s-Sweden to address the integration testing challenges of the software part of the ABB Ability 800xA distributed control systems.<\/p>\n

    While by no means this work alone answers all the integration testing challenges of our industrial partner in particular and industry in general, yet it serves as an example and step towards this goal, and also to facilitate knowledge transfer by making research solutions usable and applicable in industry.<\/p>\n

    For instance, the definition-use data flow analysis that is automated in the analysis engine of IntegrationDistiller is a well-known technique in the literature, yet not prevalent and commonly used in industry (partly due to the lack of tool support and automation). However, IntegrationDistiller, among other things, enables testers to benefit from the result of this technique and apply it implicitly under the hood of its code analysis engine without the need to know much details about the technique itself.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Introduction to IntegrationDistiller, a new automated solution to help in the testing of component integration scenarios, by Mehrdad Saadatmand. The paper has been published at the IEEE International Conference on Industrial Technology, ICIT 2019 Software systems typically consist of various interacting components and units. While these components can be tested and shown to work correctly […]<\/p>\n","protected":false},"author":2,"featured_media":609,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"categories":[23],"tags":[117,92,19,110],"_links":{"self":[{"href":"https:\/\/megamart2-ecsel.eu\/wp-json\/wp\/v2\/posts\/608"}],"collection":[{"href":"https:\/\/megamart2-ecsel.eu\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/megamart2-ecsel.eu\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/megamart2-ecsel.eu\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/megamart2-ecsel.eu\/wp-json\/wp\/v2\/comments?post=608"}],"version-history":[{"count":0,"href":"https:\/\/megamart2-ecsel.eu\/wp-json\/wp\/v2\/posts\/608\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/megamart2-ecsel.eu\/wp-json\/wp\/v2\/media\/609"}],"wp:attachment":[{"href":"https:\/\/megamart2-ecsel.eu\/wp-json\/wp\/v2\/media?parent=608"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/megamart2-ecsel.eu\/wp-json\/wp\/v2\/categories?post=608"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/megamart2-ecsel.eu\/wp-json\/wp\/v2\/tags?post=608"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}