2012
DOI: 10.1002/stvr.429
|View full text |Cite
|
Sign up to set email alerts
|

A testing strategy for abstract classes

Abstract: One of the characteristics of the increasingly widespread use of object-oriented libraries and the resulting intensive use of inheritance is the proliferation of dependencies on abstract classes. Since abstract classes cannot be instantiated, they cannot be tested in isolation using standard execution-based testing strategies. A standard approach to testing abstract classes is to instantiate a concrete descendant class and test the features that are inherited.This paper presents a structured approach that supp… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
7
0

Year Published

2014
2014
2023
2023

Publication Types

Select...
5

Relationship

0
5

Authors

Journals

citations
Cited by 7 publications
(7 citation statements)
references
References 19 publications
0
7
0
Order By: Relevance
“…Thus, for the preliminary reliability analysis of the designed application, Equation (3) was considered to be adequate and hence applied. When the failure rate is constant, the reliability function can be expressed exponentially in terms of time t and failure rate θ (18) : …”
Section: Methodsmentioning
confidence: 99%
“…Thus, for the preliminary reliability analysis of the designed application, Equation (3) was considered to be adequate and hence applied. When the failure rate is constant, the reliability function can be expressed exponentially in terms of time t and failure rate θ (18) : …”
Section: Methodsmentioning
confidence: 99%
“…Testing abstract classes is not paid much attention to in the literature [4]. The inability to instantiate objects of an abstract class is mentioned as a reason, thereby preventing them from being executed at runtime [4].…”
Section: Related Workmentioning
confidence: 99%
“…Clarke et al [4] gives general advice about the minimal set of test cases that should be used, for instance, that in the case of a concrete method that references abstract methods, there should be a test case for each class that implements such an abstract method. No attention is given to how one ensures that the right tests are developed.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…However, for the CITO problem, most existing solutions ignored the influence of abstract classes or polymorphism. That is, they did not consider the influence of either abstract classes or polymorphism . On one hand, abstract classes cannot be instantiated, making some testing levels infeasible .…”
Section: Introductionmentioning
confidence: 99%