Measuring design testability of a UML class diagram

Baudry, Benoît; Traon, Yves Le

doi:10.1016/j.infsof.2005.01.006

Cited by 35 publications

(20 citation statements)

References 30 publications

(30 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Testability is defined and measured at different levels of testing: unit testing [12], integration testing, system testing [36]; and also for different artifacts, i.e., design [38] and source code [12]. Bruntink et al [12] proposed the usage of a pool of OO class metrics-namely LOC, Fan-Out, Number of Fields (NOF), Number of Methods (NOM), Response For Classes (RFC), and Weighted Method Complexity (WMC)-to predict the testability of a class.…”

Section: B Testability and Unit Testing Strategiesmentioning

confidence: 99%

A Study on the Relation between Antipatterns and the Cost of Class Unit Testing

Sabané

Penta

Antoniol

et al. 2013

2013 17th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

Abstract-Antipatterns are known as recurring, poor design choices; recent and past studies indicated that they negatively affect software systems in terms of understandability and maintainability, also increasing change-and defect-proneness. For this reason, refactoring actions are often suggested. In this paper, we investigate a different side-effect of antipatterns, which is their effect on testability and on testing cost in particular. We consider as (upper bound) indicator of testing cost the number of test cases that satisfy the minimal data member usage matrix (MaDUM) criterion proposed by Bashir and Goel. A study-carried out on four Java programs, Ant 1.8.3, ArgoUML 0.20, CheckStyle 4.0, and JFreeChart 1.0.13-supports the evidence that, on the one hand, antipatterns unit testing requires, on average, a number of test cases substantially higher than unit testing for non-antipattern classes. On the other hand, antipattern classes must be carefully tested because they are more defect-prone than other classes. Finally, we illustrate how specific refactoring actions-applied to classes participating in antipatterns-could reduce testing cost.

show abstract

Section: B Testability and Unit Testing Strategiesmentioning

confidence: 99%

A Study on the Relation between Antipatterns and the Cost of Class Unit Testing

Sabané

Penta

Antoniol

et al. 2013

2013 17th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

show abstract

“…One limitation of this study is the late detection of errors, which makes any repair expensive. Without empirical validation, Baudry et al [15] aimed to detect the weaknesses of a UML class diagram to reduce the final testing effort. They addressed two configurations in a UML class diagram that can lead to code difficulties in testing.…”

Section: Related Workmentioning

confidence: 99%

An Empirical Analysis of the Relationship between Cohesion and Testing Effort

Albattah¹,

Melton²

2017

JSW

View full text Add to dashboard Cite

Predicting software testability can reduce costs and efforts. Cohesion, as one of software quality metrics, found to be good indicator for software testability. Although there is a good interest in software testability on the class level in the literature, software testability on the package level has not received the same interest. The paper investigates the relationship between a newly proposed package cohesion metric and software testing effort. The empirical analysis used data collected from five Java open source software systems for which JUnit test classes are available. The results show that as good the package cohesion is, as the less testing effort is needed. The stability of the correlations allows us to draw optimistic conclusions about its use as an indicator.

show abstract

“…Aranha et al [8] proposed an estimation model for test execution effort based on test specification. Baudry et al [7] proposed the testing effort estimation based on UML class diagram. Kushwala et al [14] discusses cognitive information complexity measure and modeling of test effort based on Commercial off The Shelf (COTS) components and Component Based Software Engineering (CBSE).…”

Section: Veenandaal Et Almentioning

confidence: 99%

“…Nageswaran [6] applied the use case points to estimate the effort involved in software acceptance testing based on the use case diagram. Baudry et al [7] proposed the testing effort estimation based on the UML class diagram. Aranha et al [8] proposed an estimation model for test execution effort based on the test specification.…”

Section: Introductionmentioning

confidence: 99%

Test Size Estimation for Object Oriented Software Based on Analysis Model

Arumugam¹,

Babu²

2015

JSW

View full text Add to dashboard Cite

Software test size estimation at the early analysis phase of software development lifecycle is crucial for predicting the associated effort and cost. This paper proposes a new method namely System Test Size Point (STSP) to estimate the system testing size of the object oriented software. The novel approach for the system test size estimation at the analysis phase is based on the Use Case Model (UCM) which adapts the Function Point Analysis (FPA) technique. The various features such as use case graph, test set, test set suite, relationships, main flow and alternate flow, are extracted from the UCM. Based on this, UCM components for estimation are derived. The FPA components are appropriately mapped to the UCM components and the complexity based on the weightage is specified to calculate the STSP. This proposed test size estimation approach has been evaluated with the object oriented software developed in our software engineering laboratory to assess its ability to predict the system test size.

show abstract

Measuring design testability of a UML class diagram

Cited by 35 publications

References 30 publications

A Study on the Relation between Antipatterns and the Cost of Class Unit Testing

A Study on the Relation between Antipatterns and the Cost of Class Unit Testing

An Empirical Analysis of the Relationship between Cohesion and Testing Effort

Test Size Estimation for Object Oriented Software Based on Analysis Model

Contact Info

Product

Resources

About