The TDD-guide training and guidance tool for test-driven development

Oren Mishali, Yael Dubinsky, Shmuel Katz

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

A tool is presented for guiding Test-Driven Development (TDD), called TDD-Guide. The tool is integrated into an existing development environment and guides the developer during the development by providing notifications that encourage use of TDD. The TDD practice is defined through rules that can easily be changed and are used to generate code incorporated to a development environment using an aspect-based framework, so that the development of the tool has agile characteristics. Feedback from user experiments both validates the rules and suggests refinements to improve TDD-Guide, as is shown in descriptions of two user experiments.

Original languageEnglish
Title of host publicationAgile Processes in Software Engineering and Extreme Programming - 9th International Conference, XP 2008, Proceedings
PublisherSpringer Verlag
Pages63-72
Number of pages10
ISBN (Print)3540682546, 9783540682547
DOIs
StatePublished - 2008
Externally publishedYes
Event9th International Conference on Agile Processes in Software Engineering and Extreme Programming, XP 2008 - Limerick, Ireland
Duration: 10 Jun 200814 Jun 2008

Publication series

NameLecture Notes in Business Information Processing
Volume9 LNBIP
ISSN (Print)1865-1348

Conference

Conference9th International Conference on Agile Processes in Software Engineering and Extreme Programming, XP 2008
Country/TerritoryIreland
CityLimerick
Period10/06/0814/06/08

Keywords

  • Rule-based framework
  • Software process support
  • Test driven development (TDD)
  • User evaluation

ASJC Scopus subject areas

  • Control and Systems Engineering
  • Management Information Systems
  • Business and International Management
  • Information Systems
  • Modeling and Simulation
  • Information Systems and Management

Fingerprint

Dive into the research topics of 'The TDD-guide training and guidance tool for test-driven development'. Together they form a unique fingerprint.

Cite this