Test Driven Development: By Example

By Beck. 2002

2,157 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Citations in the corpus

Counterexample-Driven Genetic Programming: Heuristic Program Synthesis from Formal Specifications (2018, background): “The reader familiar with contemporary software engineering has likely noticed that CDGP can be seen as an automatic analog to test-driven software development (Beck, 2002), where a software developer iteratively constructs tests of gradually increasing difficulty that detect flaws in the current imp”
Misleading Failures of Partial-input Baselines (2019, background): “In other words, if we could write down all the necessary tests for test-driven development (Beck, 2002) of a machine learning model, we would already have a rule-based system that can solve our task.”
Agent-Based Modeling in Marketing: Guidelines for Rigor (2011, background): “Unit testing (Beck, 2002) is where every unit or section of code has a test written for it.”
The fallacy of inscrutability (2018, background): “constitute a de facto specification for a system [27].”
Agile requirements engineering practices and challenges: an empirical study (2007, methodology): “Another technique commonly used to validate requirements is Test-Driven Development (TDD), an evolutionary approach in which tests are developed before a new functional code is written (Astels, 2003; Beck, 2003) .”
Test Driven Development (2005, background): “//Definer de parametre resourceReaderServicen forventes at blive kald med object[] resourceParams = new object[3]; resourceParams[0] = new IsEqual("GUI_WebKomponent"); resourceParams[1] = new IsEqual("L_Ansvarlig_Titel");”
Mayavi: 3D Visualization of Scientific Data (2010, result): “the code reliable is our focus on being able to script the API as much as possible. This was achieved in part by resorting to unit testing, integration testing, and some Test-Driven Development (TDD) [15]. Testing and good example scripts forced us to make the API highly reusable and resulted in inc”
Open-Source Practices for Music Signal Processing Research: Recommendations for Transparent, Sustainable, and Reproducible Audio Research (2019, methodology): “Test-driven development (TDD) is a software development process in which the specification is written before the actual development of features, and the implementations of features are then made to pass the tests [38].”
Automatic test-based assessment of programming: A review (2005, methodology): “Indeed, software development approaches like extreme programming (or XP) advocate test-first strategies [Beck 2003], that is, function tests are developed before or at the same time as the code that performs the required function.”
Robust Modeling in Cognitive Science (2019, unknown): “In computer science, there are established “robust coding” techniques that can help researchers address their unconscious biases, including independent implementation and test-driven development (Beck 2003).”
A Control Theory Perspective on Agile Methodology Use and Changing User Requirements (2009, methodology): “Some well-known agile methodologies include eXtreme Programming (XP) (Beck 1999), Scrum (Rising and Janoff 2000, Schwaber and Beedle 2002), Feature Driven Design (Coad et al. 1999), Test Driven Development (Beck 2003), Crystal (Cockburn 2001), and Lean Programming (Poppendeick 2001).”
IssueExec: A Test-Driven Approach for Localizing Software Engineering Issues (2026, unknown): “Publication date: May 2018.”