Article List

Aim, Fire

by Beck, Kent (2002-03-01)
Rating (0 ratings) read comments

Introduces the idea of test-first coding in which the tests are written before the code.

Copyright 2001 IEEE. Reprinted from (IEEE Software, September-October 2001). This material is posted here with permission of the IEEE. Such permission of the IEEE does not in any way imply IEEE endorsement of any of Agile Alliance’s products or services. Internal or personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution must be obtained from the IEEE by sending a blank email message to pubs-permission@ieee.org. By choosing to view this document, you agree to all provisions of the copyright laws protecting it.

The Humble Dialog Box

by Feathers, Michael (2002-01-01)
Rating 4.5 out of 5 (4 ratings) read comments

It explains how writing test-first can help resist the temptation to put application logic in our gui classes. On the road it also gives an example of mock objects.

Testing Focus Boosts XP

by Adhikari, Richard (2002-01-01)
Rating 1.0 out of 5 (1 rating) read comments

Stories emphasizing the importance and benefits of test first development and how it can liberate a team to confidently effect large changes.

Extreme Unit Testing: Ordering Test Cases to Maximize Early Testing

by Parrish, Allen; Jones, Joel ; Dixon, Brandon (2001-08-01)
Rating 1.5 out of 5 (4 ratings) read comments

This excellent paper looks at not just how to “write some tests, and write the method(s)” but also how to maximize the amount of testing with the minimum number of tests. Detailed case study of ‘test-first’ approach in an XP project. Well-documented approach on how to develop test cases before doing actual coding.

Integrating Unit Testing Into A Software Development Team's Process

by Ynchausti, Randy A. (2001-05-01)
Rating 3.0 out of 5 (1 rating) read comments

Article describing the introduction of integrated unit testing into the software development process. Article includes metrics.

The Need For Speed: Automating Acceptance Testing in an Extreme Programming Environment

by Crispin, Lisa; House, Tip; Wade, Carol (2001-05-01)
Rating (0 ratings) read comments

Well documented article on automated testing, with real life examples and a case study.

Integrating Extreme Programming and Contracts

by Heinecke, Hasko; Noack, Christian (2001-05-01)
Rating 4.0 out of 5 (2 ratings) read comments

Design by Contract is applied in an XP environment; this article discusses how this technique could be integrated as part of an XP project.

Continuous Integration

by Fowler, Martin (2001-01-01)
Rating 4.7 out of 5 (3 ratings) read comments

“Developing a disciplined and automated build process is essential to a controlled project”. This article describes the benifits of continuous integration and the major points of discussion. This includes the definition of a successful build, how often to build, master builds, and self testing code to name a few. The practice of continuous integration can be applied to any software development project, not just those using XP.

Engineering Notebook: An Extreme Programming Episode

by Martin, Robert C.; Koss, Robert S. (2001-01-01)
Rating 4.2 out of 5 (4 ratings) read comments

This article is derived from chapter 6 of the book Agile Software Development by Robert C. Martin. It consists of a dialog between the two members of a pair that is programming a bowling scoring application. The chapter shows the depth that the book reaches, although the dialog format is not used throughout the book.