The Experts below are selected from a list of 17286 Experts worldwide ranked by ideXlab platform
Ferhat Khendek - One of the best experts on this subject based on the ideXlab platform.
-
SAM - Acceptance Test Optimization
System Analysis and Modeling: Models and Reusability, 2014Co-Authors: Mohamed Mussa, Ferhat KhendekAbstract:Test case generation and execution may be time and effort consuming. At a given Testing phase, Test case execution can be optimized by avoiding the consideration of Test cases that have already been exercised in a previous phase. For instance, one can avoid Test case redundancy between Integration Testing and acceptance Testing. Characterizing this redundancy is not straightforward since some Integration Test cases are applied on an incomplete system with Test stubs emulating system components and therefore cannot be substituted to acceptance Test cases. In this paper, we propose an approach that maps acceptance Test cases to Integration Test cases and eliminates Test cases that have already been exercised on the system during the Integration Testing phase.
-
SAM - Identification and selection of interaction Test scenarios for Integration Testing
System Analysis and Modeling: Theory and Practice, 2013Co-Authors: Mohamed Mussa, Ferhat KhendekAbstract:Integration Testing checks for compatibility and interoperability between the components in the system. Integration Test models are, typically, generated independently from the other Testing level models. In our research, we aim at a model-based framework across unit, Integration, and acceptance level Testing. This paper contributes to this framework and for the generation of Integration Test models from unit Test models. More precisely, we focus on component interaction Test scenarios identification and selection. Following our approach, at each Integration step, unit Test cases with interaction scenarios involving the component and the context are identified, selected and merged to build the Integration Test model for the next step. Unit Test stubs and drivers are reused in the Integration Test model. Redundant Test cases are eliminated from the generated Test models.
-
SDL Forum - Towards a model based approach for Integration Testing
Lecture Notes in Computer Science, 2011Co-Authors: Mohamed Mussa, Ferhat KhendekAbstract:In this paper, we introduce a model based approach for Integration Test cases generation. The approach is based on UML 2 Testing Profile and follows the Mode-Driven Architecture for generating Integration Test cases from unit Test models. The generated Test models can be exported to Test execution environments such as JUnit and TTCN-3 for execution and evaluation.
Mohamed Mussa - One of the best experts on this subject based on the ideXlab platform.
-
SAM - Acceptance Test Optimization
System Analysis and Modeling: Models and Reusability, 2014Co-Authors: Mohamed Mussa, Ferhat KhendekAbstract:Test case generation and execution may be time and effort consuming. At a given Testing phase, Test case execution can be optimized by avoiding the consideration of Test cases that have already been exercised in a previous phase. For instance, one can avoid Test case redundancy between Integration Testing and acceptance Testing. Characterizing this redundancy is not straightforward since some Integration Test cases are applied on an incomplete system with Test stubs emulating system components and therefore cannot be substituted to acceptance Test cases. In this paper, we propose an approach that maps acceptance Test cases to Integration Test cases and eliminates Test cases that have already been exercised on the system during the Integration Testing phase.
-
SAM - Identification and selection of interaction Test scenarios for Integration Testing
System Analysis and Modeling: Theory and Practice, 2013Co-Authors: Mohamed Mussa, Ferhat KhendekAbstract:Integration Testing checks for compatibility and interoperability between the components in the system. Integration Test models are, typically, generated independently from the other Testing level models. In our research, we aim at a model-based framework across unit, Integration, and acceptance level Testing. This paper contributes to this framework and for the generation of Integration Test models from unit Test models. More precisely, we focus on component interaction Test scenarios identification and selection. Following our approach, at each Integration step, unit Test cases with interaction scenarios involving the component and the context are identified, selected and merged to build the Integration Test model for the next step. Unit Test stubs and drivers are reused in the Integration Test model. Redundant Test cases are eliminated from the generated Test models.
-
SDL Forum - Towards a model based approach for Integration Testing
Lecture Notes in Computer Science, 2011Co-Authors: Mohamed Mussa, Ferhat KhendekAbstract:In this paper, we introduce a model based approach for Integration Test cases generation. The approach is based on UML 2 Testing Profile and follows the Mode-Driven Architecture for generating Integration Test cases from unit Test models. The generated Test models can be exported to Test execution environments such as JUnit and TTCN-3 for execution and evaluation.
Milton E Strauss - One of the best experts on this subject based on the ideXlab platform.
-
optimization and validation of a visual Integration Test for schizophrenia research
Schizophrenia Bulletin, 2012Co-Authors: Steven M Silverstein, Brian P Keane, M Deanna, Cameron S Carter, James M Gold, Ilona Kovacs, Angus W Macdonald, Daniel J Ragland, Milton E StraussAbstract:The Cognitive Neuroscience Treatment Research to Improve Cognition in Schizophrenia initiative highlighted a contour Integration Test as a promising index of visual Integration impairment because of its well-established psychometric properties; its prior validation in healthy adults, patients, and nonhuman primates; and its potential sensitivity to treatment effects. In this multisite study, our goals were to validate the task on the largest subject sample to date, clarify the task conditions and number of trials that best discriminate patients from controls, and determine whether this discrimination can occur in standard clinical trial settings. For our task, subjects briefly observed a field of disconnected, oriented elements and attempted to decide whether a subset of those elements formed a leftward- or rightward-pointing shape. Difficulty depended on the amount of orientational jitter that was added to the shape’s elements. Two versions of this Jittered Orientation Visual Integration task (JOVI) were examined. Study 1 did not reveal between-group differences in threshold (ie, the jitter magnitude needed to reach a performance level of ~80%), but this likely owed to the wide sampling distribution of jitter levels and resulting floor/ceiling effects in many conditions. Study 2 incorporated a narrower range of difficulty levels and revealed lower thresholds (worse performance) among patients (p < .001). This group difference remained even when only the first half of the trials was analyzed (p = .001). Thus, the JOVI-2 provides a brief, sensitive measure of visual Integration deficits in schizophrenia. Neural implications and potential future applications of the JOVI are discussed.
Klaus Pohl - One of the best experts on this subject based on the ideXlab platform.
-
Integration Testing in software product line engineering a model based technique
Fundamental Approaches to Software Engineering, 2007Co-Authors: Sacha Reis, Andreas Metzger, Klaus PohlAbstract:The development process in software product line engineering is divided into domain engineering and application engineering. As a consequence of this division, Tests should be performed in both processes. However, existing Testing techniques for single systems cannot be applied during domain engineering, because of the variability in the domain artifacts. Existing software product line Test techniques only cover unit and system Tests. Our contribution is a model-based, automated Integration Test technique that can be applied during domain engineering. For generating Integration Test case scenarios, the technique abstracts from variability and assumes that placeholders are created for variability. The generated scenarios cover all interactions between the integrated components, which are specified in a Test model. Additionally, the technique reduces the effort for creating placeholders by minimizing the number of placeholders needed to execute the Integration Test case scenarios. We have experimentally measured the performance of the technique and the potential reduction of placeholders.
Zsuzsanna Marian - One of the best experts on this subject based on the ideXlab platform.
-
An effective approach for determining the class Integration Test order using reinforcement learning
Applied Soft Computing, 2018Co-Authors: Gabriela Czibula, Istvan Gergely Czibula, Zsuzsanna MarianAbstract:Abstract Within the software Testing domain, determining the order in which classes are Tested in Integration Testing is an important problem called class Integration Test order identification (CITO). This problem is useful in Integration Testing, as it contributes to reducing the time needed for Testing a software system and refers to the process of identifying an optimal order in which the application classes should be combined and Tested as a group. This paper introduces a novel approach based on reinforcement learning for class Integration Test order optimization in the context of Integration Testing. The experimental evaluation is performed on four synthetic examples and on six existing software systems often used in the literature for this problem. The results obtained are analyzed and compared to similar related work from the literature, highlighting the potential of the current proposal. The proposed reinforcement learning based approach outperforms most methods existing in the software engineering literature for optimizing the Test order for class-based Integration. Moreover, it is general, and can be easily extended for optimizing the order in which software components should be Tested during component Integration Testing of a software system.
