scholarly journals Investigating the Prioritization of Unit Testing Effort using Software Metrics

2017 ◽  
Author(s):  
Fadel Toure ◽  
Mourad Badri ◽  
Luc Lamontagne
Keyword(s):  
Software Metrics ◽  
Unit Testing ◽  
Testing Effort

Investigating the Effect of Aspect-Oriented Refactoring on the Unit Testing Effort of Classes: An Empirical Evaluation

2017 ◽  
Vol 27 (05) ◽  
pp. 749-789 ◽  
Author(s):  
Mourad Badri ◽  
Aymen Kout ◽  
Linda Badri
Keyword(s):  
Statistical Tests ◽  
Source Code ◽  
Empirical Evaluation ◽  
Software Systems ◽  
Test Cases ◽  
Unit Testing ◽  
Unit Test ◽  
Testing Effort ◽  
Using Data ◽  
The Impact

This paper aims at investigating empirically the effect of aspect-oriented (AO) refactoring on the unit testability of classes in object-oriented software. The unit testability of classes has been addressed from the perspective of the unit testing effort, and particularly from the perspective of the unit test cases (TCs) construction. We investigated, in fact, different research questions: (1) the impact of AO refactoring on source code attributes (size, complexity, coupling, cohesion and inheritance), attributes that are mostly related to the unit testability of classes, (2) the impact of AO refactoring on unit test code attributes (size, assertions, invocations and data creation), attributes that are indicators of the effort involved to write the code of unit TCs, and (3) the relationships between the variations observed after AO refactoring in both source code and unit test code attributes. We used in the study different techniques: correlation analysis, statistical tests and linear regression. We performed an empirical evaluation using data collected from three well-known open source (Java) software systems (JHOTDRAW, HSQLBD and PETSTORE) that have been refactored using AO programming (AspectJ). Results suggest that: (1) overall, the effort involved in the construction of unit TCs of refactored classes has been reduced, (2) the variations of source code attributes have more impact on methods invocation between unit TCs, and finally (3) the variations of unit test code attributes are more influenced by the variation of the complexity of refactored classes compared to the other class attributes.

Testing-Effort Dependent Software Reliability Model for Distributed Systems

2013 ◽  
Vol 4 (2) ◽  
pp. 1-14 ◽  
Author(s):  
Omar Shatnawi
Keyword(s):  
Distributed Systems ◽  
Software Development ◽  
Software Reliability ◽  
Software Metrics ◽  
Calendar Time ◽  
Development Environment ◽  
Client Server ◽  
Testing Effort ◽  
Computer Based ◽  
Fault Removal

Distributed systems are being developed in the context of the client-server architecture. Client-server architectures dominate the landscape of computer-based systems. Client-server systems are developed using the classical software engineering activities. Developing distributed systems is an activity that consumes time and resources. Even if the degree of automation of software development activities increased, resources are an important limitation. Reusability is widely believed to be a key direction to improving software development productivity and quality. Software metrics are needed to identify the place where resources are needed; they are an extremely important source of information for decision making. In this paper, an attempt has been made to describe the relationship between the calendar time, the fault removal process and the testing-effort consumption in a distributed development environment. Software fault removal phenomena and testing-effort expenditures are described by a non-homogenous Poisson process (NHPP) and testing-effort curves respectively. Actual software reliability data cited in literature have been used to demonstrate the proposed model. The results are fairly encouraging.

scholarly journals Evaluating the Effect of Control Flow on the Unit Testing Effort of Classes: An Empirical Analysis

2012 ◽  
Vol 2012 ◽  
pp. 1-13 ◽  
Author(s):  
Mourad Badri ◽  
Fadel Toure
Keyword(s):  
Operating Characteristic ◽  
Control Flow ◽  
Software Systems ◽  
Test Cases ◽  
Unit Testing ◽  
Testing Effort ◽  
Logistic Regression Method ◽  
Predicted Model ◽  
Object Oriented Systems ◽  
The Relationship

The aim of this paper is to evaluate empirically the relationship between a new metric (Quality Assurance Indicator—Qi) and testability of classes in object-oriented systems. The Qi metric captures the distribution of the control flow in a system. We addressed testability from the perspective of unit testing effort. We collected data from five open source Java software systems for which JUnit test cases exist. To capture the testing effort of classes, we used different metrics to quantify the corresponding JUnit test cases. Classes were classified, according to the required testing effort, in two categories: high and low. In order to evaluate the capability of the Qi metric to predict testability of classes, we used the univariate logistic regression method. The performance of the predicted model was evaluated using Receiver Operating Characteristic (ROC) analysis. The results indicate that the univariate model based on the Qi metric is able to accurately predict the unit testing effort of classes.

Approach to constructing software unit testing tools

1995 ◽  
Vol 10 (6) ◽  
pp. 245 ◽  
Author(s):  
Gang Luo ◽  
Robert L. Probert ◽  
Hasan Ural
Keyword(s):  
Unit Testing ◽  
Testing Tools

Developing a Web-based Application for Energy Supply Systems

2019 ◽  
Vol 2 (3) ◽  
pp. 164-169
Author(s):  
Mohammed Faza ◽  
Maulahikmah Galinium ◽  
Matthias Guenther
Keyword(s):  
Energy Supply ◽  
Power Plants ◽  
Acceptance Testing ◽  
Design Activity ◽  
Unit Testing ◽  
Validity Testing ◽  
Energy Supply System ◽  
Time Series Modelling ◽  
Supply Systems ◽  
Energy Supply Systems

An energy supply system consists of a system of power plants and transmission anddistribution systems that supply electrical energy. The present project is limited to the modellingof the generation system. Its objective is the design and implementation of a web-basedapplication for simulating energy supply systems using the Laravel framework. The projectfocuses on six modules representing geothermal energy, solar energy, biopower, hydropower,storage, and fossil-based energy that are allocated to satisfy a given power demand. It isexecuted as a time series modelling for an exemplary year with hourly resolution. Thedevelopment of the software is divided into four steps, which are the definition of the userrequirements, the system design (activity, use case, system architecture, and ERD), the softwaredevelopment, and the software testing (unit testing, functionality testing, validity testing, anduser acceptance testing). The software is successfully implemented. All the features of thesoftware work as intended. Also, the software goes through validity testing using three differentinput data, to make sure the software is accurate. The result of the testing is 100% accuracy withrespect to the underlying model that was implemented in an excel calculation.

Neural Network Model to Calculate the Creep Data Using Size

2017 ◽  
Vol 7 (8) ◽  
pp. 257
Author(s):  
Seetharam .K ◽  
Sharana Basava Gowda ◽  
. Varadaraj
Keyword(s):  
Neural Network ◽  
Risk Factors ◽  
Software Engineering ◽  
Network Model ◽  
Neural Network Model ◽  
Software Metrics ◽  
Creep Data ◽  
Engineering Software ◽  
Function Points ◽  
Different Levels

In Software engineering software metrics play wide and deeper scope. Many projects fail because of risks in software engineering development[1]t. Among various risk factors creeping is also one factor. The paper discusses approximate volume of creeping requirements that occur after the completion of the nominal requirements phase. This is using software size measured in function points at four different levels. The major risk factors are depending both directly and indirectly associated with software size of development. Hence It is possible to predict risk due to creeping cause using size.

Sign in / Sign up

Export Citation Format

Share Document