By the same authors

Contract driven development= test driven development-writing test cases

Research output: Contribution to conferencePaper

Standard

Contract driven development= test driven development-writing test cases. / Leitner, Andreas; Ciupa, Ilinca; Oriol, Manuel; Meyer, Bertrand; Fiva, A.

2007. 434.

Research output: Contribution to conferencePaper

Harvard

Leitner, A, Ciupa, I, Oriol, M, Meyer, B & Fiva, A 2007, 'Contract driven development= test driven development-writing test cases' pp. 434. https://doi.org/10.1145/1287624.1287685

APA

Leitner, A., Ciupa, I., Oriol, M., Meyer, B., & Fiva, A. (2007). Contract driven development= test driven development-writing test cases. 434. https://doi.org/10.1145/1287624.1287685

Vancouver

Leitner A, Ciupa I, Oriol M, Meyer B, Fiva A. Contract driven development= test driven development-writing test cases. 2007. https://doi.org/10.1145/1287624.1287685

Author

Leitner, Andreas ; Ciupa, Ilinca ; Oriol, Manuel ; Meyer, Bertrand ; Fiva, A. / Contract driven development= test driven development-writing test cases.

Bibtex - Download

@conference{c3e164a769134c78be2d25a3cb3238c7,
title = "Contract driven development= test driven development-writing test cases",
abstract = "Although unit tests are recognized as an important tool in software development, programmers prefer to write code, rather than unit tests. Despite the emergence of tools like JUnit which automate part of the process, unit testing remains a time-consuming, resource-intensive, and not particularly appealing activity.This paper introduces a new development method, called Contract Driven Development. This development method is based on a novel mechanism that extracts test cases from failure-producing runs that the programmers trigger. It exploits actions that developers perform anyway as part of their normal process of writing code. Thus, it takes the task of writing unit tests off the developers' shoulders, while still taking advantage of their knowledge of the intended semantics and structure of the code. The approach is based on the presence of contracts in code, which act as the oracle of the test cases. The test cases are extracted completely automatically, are run in the background, and can easily be maintained over versions. The tool implementing this methodology is called Cdd and is available both in binary and in source form.",
author = "Andreas Leitner and Ilinca Ciupa and Manuel Oriol and Bertrand Meyer and A. Fiva",
year = "2007",
doi = "10.1145/1287624.1287685",
language = "Undefined/Unknown",
pages = "434",

}

RIS (suitable for import to EndNote) - Download

TY - CONF

T1 - Contract driven development= test driven development-writing test cases

AU - Leitner, Andreas

AU - Ciupa, Ilinca

AU - Oriol, Manuel

AU - Meyer, Bertrand

AU - Fiva, A.

PY - 2007

Y1 - 2007

N2 - Although unit tests are recognized as an important tool in software development, programmers prefer to write code, rather than unit tests. Despite the emergence of tools like JUnit which automate part of the process, unit testing remains a time-consuming, resource-intensive, and not particularly appealing activity.This paper introduces a new development method, called Contract Driven Development. This development method is based on a novel mechanism that extracts test cases from failure-producing runs that the programmers trigger. It exploits actions that developers perform anyway as part of their normal process of writing code. Thus, it takes the task of writing unit tests off the developers' shoulders, while still taking advantage of their knowledge of the intended semantics and structure of the code. The approach is based on the presence of contracts in code, which act as the oracle of the test cases. The test cases are extracted completely automatically, are run in the background, and can easily be maintained over versions. The tool implementing this methodology is called Cdd and is available both in binary and in source form.

AB - Although unit tests are recognized as an important tool in software development, programmers prefer to write code, rather than unit tests. Despite the emergence of tools like JUnit which automate part of the process, unit testing remains a time-consuming, resource-intensive, and not particularly appealing activity.This paper introduces a new development method, called Contract Driven Development. This development method is based on a novel mechanism that extracts test cases from failure-producing runs that the programmers trigger. It exploits actions that developers perform anyway as part of their normal process of writing code. Thus, it takes the task of writing unit tests off the developers' shoulders, while still taking advantage of their knowledge of the intended semantics and structure of the code. The approach is based on the presence of contracts in code, which act as the oracle of the test cases. The test cases are extracted completely automatically, are run in the background, and can easily be maintained over versions. The tool implementing this methodology is called Cdd and is available both in binary and in source form.

U2 - 10.1145/1287624.1287685

DO - 10.1145/1287624.1287685

M3 - Paper

SP - 434

ER -