Testability has always been a difficult exercise and its accurate estimation or assessment a complex exercise. Most of the studies quantify testability or more specifically the attributes that have influence on software testability but at the implementation level. A decision to transform the design in order to improve software testability after implementation has started may be very error prone...

Testability is a quality factor used to predict the amount of effort required for software testing and to indicate the difficulty of revealing faults. Also, it can be used to estimate the difficulty of software testing. This paper presents a quantitative testability analysis method for a software component that can be used when the source program is not available, but the bytecode is (as in Jav...

Testability is the degree to which a software artifact facilitates testing in a given test context. It is directly related to test effort reduction. A lack of testability, like other design faults, is expensive to repair when detected late during software development. Therefore, testability should be addressed already during reviews of early development artifacts. This paper describes different...

This paper introduces the notion of ‘co-testability transformation’. As opposed to traditional testability transformations, which replace the original program in testing, co-testability transformations are designed to be used in conjunction with the original program (and any additional co-transformations as well). Until now, testability transformations have only been used to improve test data g...

The objective of the IEEE P1522 Testability and Diagnosability Metrics standard is to provide notionally correct and mathematically precise definitions of testability measures that may be used to either measure the testability characteristics of a system, or predict the testability of a system. Notionally correct means that the measures are not in conflict with intuitive and historical represen...

This paper presents a Computer Aided Testability tool named STA (System Testability Assistant), aiming at proposing a testa-bility strategy for systems as early as possible in the design process. Given a system description, STA rst compiles it in order to create system, boards, and circuits objects, and then proceeds bottom-up, from the circuit to the system, in order to evaluate the actual tes...

Software testing is one of the most expensive phase of the software development life cycle. Testing object oriented software is more expensive due to various features like abstraction, inheritance etc. The cost of testing can be reduced by improving the software testability. Software testability of a class is generally measured in terms of the testing effort which is equal to the number of test...

Measuring testability early in the development life cycle especially at design phase is a criterion of crucial importance to software designers, developers, quality controllers and practitioners. However, most of the mechanism available for testability measurement may be used in the later phases of development life cycle. Early estimation of testability, absolutely at design phase helps designe...

Testability, and design for testability, are widely discussed practical issues in software engineering, especially in protocol engineering. Existing definitions (or circumscriptions) of testability seem to be either quite vague, or, if more or less formal, then dedicated only to very special system models. Testability is usually decomposed into aspects like observability and controllability, an...

This paper addresses not only the question of testability measurement of OO designs but also focuses on its practicability. While detecting testability weaknesses (called testability anti-patterns) of an OO design is a crucial task, one cannot expect from a non-specialist to make the right improvements, without guidance or automation. To overcome this limitation, this paper investigates solutio...