Metrics for Test Case Design in Test Driven Development

Shrivastava, Divya; Jain, Rishabh

doi:10.7763/ijcte.2010.v2.269

Cited by 10 publications

(8 citation statements)

References 4 publications

(12 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Shrivastava and Jain considered the metrics proposed by [11] and defined in [12] an index of testability for a class. Their purpose was to investigate metrics from the perspective related to the design of unit test cases.…”

Section: State-of-the-artmentioning

confidence: 99%

On the Evaluation of Software Maintainability Using Automatic Test Case Generation

Nogueira

Ribeiro

Zenha-Rela

2014

2014 9th International Conference on the Quality of Information and Communications Technology

View full text Add to dashboard Cite

The measurement of external software attributes and the analysis of how those attributes have evolved through the software's releases are challenging activities. This is particularly evident when we discuss the maintainability of Object-Oriented (OO) systems which, due to their specific characteristics, hide information that cannot be gathered through static analysis. As maintainability can be defined as the "speed and ease with which a program can be corrected or changed", we believe that test data are reflective of the changes performed during maintenance. Moreover, empirical observations allow to speculate about the relationships between maintainability and the behaviour of the software when executed by test cases (e.g., coverage values) and the test cases' characteristics (e.g., generation time). Our aim is to complement the state-of-the art by proposing a new approach for understanding and characterizing the maintainability of OO systems, which makes use of test data and of the information gathered from the tests' execution.

show abstract

Section: State-of-the-artmentioning

confidence: 99%

On the Evaluation of Software Maintainability Using Automatic Test Case Generation

Nogueira

Ribeiro

Zenha-Rela

2014

2014 9th International Conference on the Quality of Information and Communications Technology

View full text Add to dashboard Cite

show abstract

“…In [3], a set of design metrics, called as Automated Test Case for Unit Testing (ATCUT), was designed in order to predict the effort required for unit testing. Shrivastava and Jain considered the metrics proposed by [15] and defined an index of testability for a class.…”

Section: Introductionmentioning

confidence: 99%

Predicting software complexity by means of evolutionary testing

Nogueira

2012

Proceedings of the 27th IEEE/ACM International Conference on Automated Software Engineering

View full text Add to dashboard Cite

One characteristic that impedes software from achieving good levels of maintainability is the increasing complexity of software. Empirical observations have shown that typically, the more complex the software is, the bigger the test suite is. Thence, a relevant question, which originated the main research topic of our work, has raised: "Is there a way to correlate the complexity of the test cases utilized to test a software product with the complexity of the software under test? ". This work presents a new approach to infer software complexity with basis on the characteristics of automatically generated test cases. From these characteristics, we expect to create a test case profile for a software product, which will then be correlated to the complexity, as well as to other characteristics, of the software under test. This research is expected to provide developers and software architects with means to support and validate their decisions, as well as to observe the evolution of a software product during its lifecycle. Our work focuses on object-oriented software, and the corresponding test suites will be automatically generated through an emergent approach for creating test data named as Evolutionary Testing.

show abstract

“…Shrivastava and Jain study unit test case design metrics in TDD [10]. Although their work does not target safety-critical software development they propose useful metrics for TDD in general.…”

Section: Test Driven Developmentmentioning

confidence: 99%

Test-Driven Approach for Safety-Critical Software Development

Özçelik

Altılar²

2020

JSW

View full text Add to dashboard Cite

Nowadays software control large majority of systems that humankind use. Systems that software is used widely, such as transportation, military, medicine and avionics must be safe during operation. Fail in these critical systems may cause catastrophic results (i.e. loss of human life, loss or severe damage to environment or equipment etc.). In order to avoid failure on safety critical systems or at least mitigate risks detailed testing is required. Many safety critical systems are developed with sequential phases and tested with test last approach. But test last approach is not sufficient when requirements are unclear or changed. To overcome weaknesses of test last approach we propose test driven approach for safety critical software development, regulated by IEC 61508 standard. A systematic analysis of IEC 61508 software requirements against proposed approach showed that the approach directly supports some objectives and partially supports some of them. Supported objectives are safety requirement identification, simple and testable software design, verification and validation. In general introduced approach suits regulated software development well and this paper outlines these details.

show abstract

Metrics for Test Case Design in Test Driven Development

Cited by 10 publications

References 4 publications

On the Evaluation of Software Maintainability Using Automatic Test Case Generation

On the Evaluation of Software Maintainability Using Automatic Test Case Generation

Predicting software complexity by means of evolutionary testing

Test-Driven Approach for Safety-Critical Software Development

Contact Info

Product

Resources

About