Meszaros G. xUnit Test Patterns Refactoring Test Code

Подождите немного. Документ загружается.

This page intentionally left blank

819

References

[AP]

AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis

Published by: John Wiley (1998)

ISBN: 0-471-19713-0

By: William J. Brown et al.

This book describes common problems on software projects and suggests

how to eliminate them by changing the architecture or project organization.

[APLfPW]

A Pattern Language for Pattern Writing

In: Pattern Languages of Program Design 3 [PLoPD3], pp. 529–574.

Published by: Addison-Wesley (1998)

By: Gerard Meszaros and James Doble

As the patterns community has accumulated experience in writing and

reviewing patterns and pattern languages, we have begun to develop insight

into pattern-writing techniques and approaches that have been observed to

be particularly effective at addressing certain recurring problems. This pat-

tern language attempts to capture some of these “best practices” of pattern

writing, both by describing them in pattern form and by demonstrating them

in action. As such, this pattern language is its own running example.

Further Reading

Full text of this paper is available online in PDF form at http://Pattern-

WritingPatterns.gerardmeszaros.com and in HTML form, complete with a

hyperlinked table of contents, at http://hillside.net/patterns/writing/pattern-

writingpaper.htm.

[ARTRP]

Agile Regression Testing Using Record and Playback

http://AgileRegressionTestPaper.gerardmeszaros.com

By: Gerard Meszaros and Ralph Bohnet

This paper was presented at XP/Agile Universe 2003. It describes how we

built a “record and playback” test mechanism into a safety-critical appli-

cation to make it easier to regression test it as it was ported from OS2 to

Windows.

[CJ2EEP]

Core J2EE™ Patterns, Second Edition: Best Practices and Design Strategies

Published by: Prentice Hall (2003)

ISBN: 0-131-42246-4

By: Deepak Alur, Dan Malks, and John Crupi

This book catalogs the core patterns of usage of Enterprise Java Beans

(EJB), which are a key part of the Java 2 Enterprise Edition. Examples

include Session Facade [CJ2EEP].

[DDD]

Domain-Driven Design: Tackling Complexity in the Heart of Software

Published by: Addison-Wesley (2004)

ISBN: 0-321-12521-5

By: Eric Evans

This book is a good introduction to the process of using a domain model

as the heart of a software system.

Readers learn how to use a domain model to make complex

development effort more focused and dynamic. A core of best

practices and standard patterns provides a common language for

the development team.

References

820

[ET]

Endo-Testing

http://www.connextra.com/aboutUs/mockobjects.pdf

By: Tim Mackinnon, Steve Freeman, and Philip Craig

This paper, which was presented at XP 2000 in Sardinia, describes the use

of Mock Objects (page 544) to facilitate testing of the behavior of an object

by monitoring its behavior while it is executing.

Unit testing is a fundamental practice in eXtreme Programming,

but most nontrivial code is difﬁ cult to test in isolation. It is hard

to avoid writing test suites that are complex, incomplete, and

difﬁ cult to maintain and interpret. Using Mock Objects for

unit testing improves both domain code and test suites. These

objects allow unit tests to be written for everything, simplify

test structure, and avoid polluting domain code with testing

infrastructure.

[FaT]

Frameworks and Testing

In: Proceedings of XP2002

http://www.agilealliance.org/articles/roockstefanframeworks/ﬁ le

By: Stefan Roock

This paper is mandatory reading for framework builders. It describes four

kinds of automated testing that should accompany a framework, including

the ability to test a plug-in’s compliance with the framework’s protocol and

a testing framework that makes it easier to test applications built on the

framework.

References

821

[FitB]

Fit for Developing Software

Published by: Addison-Wesley (2005)

ISBN: 0-321-26934-9

By: Rick Mugridge and Ward Cunningham

This book is a great introduction to the use of Data-Driven Tests (page 288)

for preparing customer tests, whether as part of agile or traditional projects.

This is what I wrote for inclusion as “advance praise”:

Wow! This is the book I wish I had on my desk when I did

my ﬁ rst storytest-driven development project. It explains the

philosophy behind the Fit framework and a process for using it

to interact with the customers to help deﬁ ne the requirements of

the project. It makes Fit so easy and approachable that I wrote

my ﬁ rst FitNesse tests before I even I ﬁ nished the book.

Further Reading

More information on Fit can be found at Ward’s Web site, http://ﬁ t.c2.com.

[GOF]

Design Patterns: Elements of Reusable Object-Oriented Software

Published by: Addison-Wesley (1995)

ISBN: 0-201-63361-2

By: Erich Gamma, Richard Helm, Ralph Johnson, and John M.Vlissides

This book started the patterns movement. In it, the “Gang of Four” describe

23 recurring patterns in object-oriented software systems. Examples include

Composite [GOF], Factory Method [GOF], and Facade [GOF].

References

822

[HoN]

Hierarchy of Needs

From Wikipedia [Wp]:

Maslow’s hierarchy of needs is a theory in psychology that Abraham

Maslow proposed in his 1943 paper “A Theory of Human Motivation,”

which he subsequently extended. His theory contends that as humans meet

“basic needs,” they seek to satisfy successively “higher needs” that occupy

a set hierarchy. . . .

Maslow’s hierarchy of needs is often depicted as a pyramid consisting of

ﬁ ve levels: The four lower levels are grouped together as deﬁ ciency needs

associated with physiological needs, while the top level is termed growth

needs associated with psychological needs. While our deﬁ ciency needs must

be met, our being needs are continually shaping our behavior. The basic

concept is that the higher needs in this hierarchy only come into focus once

all the needs that are lower down in the pyramid are mainly or entirely

satisﬁ ed. Growth forces create upward movement in the hierarchy, whereas

regressive forces push prepotent needs farther down the hierarchy.

[IEAT]

Improving the Effectiveness of Automated Tests

http://FasterTestsPaper.gerardmeszaros.com.

By: Gerard Meszaros, Shaun Smith, and Jennitta Andrea

This paper was presented at XP2001 in Sardinia, Italy. It describes a number

of issues that reduce the speed and effectiveness of automated unit tests and

suggests ways to address them.

[IXP]

Industrial XP

http://ixp.industriallogic.com.

Industrial XP is a “branded” variant of eXtreme Programming created

by Joshua Kerievsky of Industrial Logic. It includes a number of practices

required to scale eXtreme Programming to work in larger enterprises, such

as “Project Chartering.”

References

823

[JBrains]

JetBrains

http://www.jetbrains.com.

JetBrains builds software development tools that automate (among other

things) refactoring. Its Web site contains a list of all refactorings that the

company’s various tools support, including some that are not described in

[Ref].

[JNI]

JUnit New Instance

http://www.martinfowler.com/bliki/JunitNewInstance.html

This article by Martin Fowler provides the background for why it makes

sense for JUnit and many of its ports to create a new instance of the Testcase

Class (page 373) for each Test Method (page 348).

[JuPG]

JUnit Pocket Guide

Published by: O’Reilly

ISBN: 0-596-00743-4

By: Kent Beck

This 80-page, small-format book is an excellent summary of key features

of JUnit and best practices for writing tests. Being small enough to ﬁ t in a

pocket, it doesn’t go into much detail, but it does give us an idea of what is

possible and where to look for details.

[LSD]

Lean Software Development : An Agile Toolkit

Published by: Addison-Wesley (2003)

ISBN: 0-321-15078-3

By: Mary Poppendieck and Tom Poppendieck

This excellent book describes 22 “thinking tools” that are used to work

quickly and effectively in many domains. The authors describe how to

apply these tools to software development. If you want to understand why

agile development methods work, this book is a must read!

References

824

[MAS]

Mocks Aren’t Stubs

http://www.martinfowler.com/articles/mocksArentStubs.html

By: Martin Fowler

This article clariﬁ es the difference between Mock Objects (page 544) and

Test Stubs (page 529). It goes on to describe the two fundamentally differ-

ent approaches to test-driven development engendered by these differences:

“classical TDD” versus “mockist TDD.”

[MRNO]

Mock Roles, Not Objects

Paper presented at OOPSLA 2004 in Vancouver, British Columbia, Canada.

By: Steve Freeman, Tim Mackinnon, Nat Pryce, and Joe Walnes

This paper describes the use of Mock Objects (page 544) to help the developer

discover the signatures of the objects on which the class being designed and

tested depends. This approach allows the design of the supporting classes to

be deferred until after the client classes have been coded and tested. Members

can obtain this paper at the ACM portal http://portal.acm.org/ft_gateway.

cfm?id=1028765&type=pdf; nonmembers of the ACM can ﬁ nd it at http://

joe.truemesh.com/MockRoles.pdf.

[PEAA]

Patterns of Enterprise Application Architecture

Published by: Addison-Wesley (2003)

ISBN: 0-321-12742-0

By: Martin Fowler

This book is an indispensable handbook of architectural patterns that

are applicable to any enterprise application platform. It is a great way

to understand how the various approaches to developing large business

systems differ.

References

825

[PiJV1]

Patterns in Java, Volume 1: A Catalog of Reusable Design Patterns Illustrated

with UML

Published by: Wiley Publishing (2002)

ISBN: 0-471-22729-3

By: Mark Grand

A catalog of design patterns commonly used in Java.