Meszaros G. xUnit Test Patterns Refactoring Test Code
Подождите немного. Документ загружается.
778
Name Page Relationship Base Name Chapter
Reuse Test for 418 Variation Creation Method Chapter 20, Fixture
Fixture Setup Setup Patterns
Reused Fixture 317 Alias Shared Fixture Chapter 18, Test
Strategy Patterns
Robot User Test 278 Alias Recorded Test Chapter 18, Test
Strategy Patterns
Robot User 299 Variation Test Automation Chapter 18, Test
Test Framework Framework Strategy Patterns
Row Test 609 Alias Parameterized Test Chapter 24, Test
Organization Patterns
SUT API 601 Alias Test Utility Chapter 24, Test
Encapsulation Method Organization
Patterns
SUT 601 Variation Test Utility Chapter 24, Test
Encapsulation Method Organization
Method Patterns
Saboteur 530 Variation Test Stub Chapter 23, Test
Double Patterns
Scripted Test 285 Scripted Test Chapter 18, Test
Strategy Patterns
Self Shunt 540 Variation Hard-Coded Chapter 23, Test
Test Double Double Patterns
Self-Describing 715 Variation Literal Value Chapter 27, Value
Value Patterns
Service Layer 339 Variation Layer Test Chapter 18, Test
Test Strategy Patterns
Service Locator 686 Alias Dependency Chapter 26, Design-
Lookup for-Testability
Patterns
Setter Injection 681 Variation Dependency Chapter 26, Design-
Injection for-Testability
Patterns
Setup Decorator 447 Setup Decorator Chapter 20, Fixture
Setup Patterns
Shared Context 317 Alias Shared Fixture Chapter 18, Test
Strategy Patterns
Shared Fixture 317 Shared Fixture Chapter 18, Test
Strategy Patterns
Patterns,
Aliases, and
Variations
Appendix G Patterns, Aliases, and Variations
779
Name Page Relationship Base Name Chapter
Shared Fixture 491 Variation Guard Assertion Chapter 21, Result
State Assertion Verifi cation Patterns
Shared Setup 424 Alias Implicit Setup Chapter 20, Fixture
Method Setup Patterns
Simple Success 349 Variation Test Method Chapter 19, xUnit
Test Basics Patterns
Single-Layer Test 337 Alias Layer Test Chapter 18, Test
Strategy Patterns
Single-Outcome 366 Variation Assertion Method Chapter 19, xUnit
Assertion Basics Patterns
Single Test Suite 593 Variation Named Test Suite Chapter 24, Test
Organization
Patterns
Slow Tests 318 Variation Shared Fixture Chapter 18, Test
Strategy Patterns
Spy 538 Alias Test Spy Chapter 23, Test
Double Patterns
Stale Fixture 317 Alias Shared Fixture Chapter 18, Test
Strategy Patterns
Standard Context 305 Alias Standard Fixture Chapter 18, Test
Strategy Patterns
Standard Fixture 305 Standard Fixture Chapter 18, Test
Strategy Patterns
State-Exposing 580 Variation Test-Specifi c Chapter 23, Test
Subclass Subclass Double Patterns
State Verifi cation 462 State Verifi cation Chapter 21, Result
Verifi cation Patterns
State-Based 462 Alias State Verifi cation Chapter 21, Result
Testing Verifi cation Patterns
Stated Outcome 366 Variation Assertion Method Chapter 19, xUnit
Assertion Basics Patterns
Statically 561 Variation Confi gurable Chapter 23, Test
Generated Test Test Double Double Patterns
Double
Stored Procedure 654 Stored Procedure Chapter 25, Database
Test Test Patterns
Stub 529 Alias Test Stub Chapter 23, Test
Double Patterns
Continued...
Patterns, Aliases, and Variations
Patterns,
Aliases, and
Variations
780
Name Page Relationship Base Name Chapter
Stub 728 Alias Dummy Object Chapter 27, Value
Patterns
Subclassed 700 Variation Humble Object Chapter 26, Design-
Humble Object for-Testability
Patterns
Subclassed 581 Alias Test-Specifi c Chapter 23, Test
Singleton Subclass Double Patterns
Subclassed 581 Alias Test-Specifi c Chapter 23, Test
Test Double Subclass Double Patterns
Subcutaneous 340 Variation Layer Test Chapter 18, Test
Test Strategy Patterns
Subset Suite 593 Variation Named Test Suite Chapter 24, Test
Organization
Patterns
Substitutable 581 Alias Test-Specifi c Chapter 23, Test
Singleton Subclass Double Patterns
Substituted 581 Variation Test-Specifi c Chapter 23, Test
Singleton Subclass Double Patterns
Suite of Suites 388 Variation Test Suite Object Chapter 19, xUnit
Basics Patterns
Suite Fixture 441 Suite Fixture Chapter 20, Fixture
Setup Setup Setup Patterns
Symbolic 715 Variation Literal Value Chapter 27, Value
Constant Patterns
Table Truncation 661 Table Truncation Chapter 25, Database
Teardown Teardown Patterns
Tabular Test 609 Variation Parameterized Chapter 24, Test
Test Organization
Patterns
Teardown 511 Variation In-line Teardown Chapter 22, Fixture
Guard Clause Teardown Patterns
Temporary 530 Variation Test Stub Chapter 23, Test
Test Stub Double Patterns
Test Automation 298 Test Automation Chapter 18, Test
Framework Framework Strategy Patterns
Test Bed 429 Alias Prebuilt Fixture Chapter 20, Fixture
Setup Patterns
Patterns,
Aliases, and
Variations
Appendix G Patterns, Aliases, and Variations
781
Name Page Relationship Base Name Chapter
Test Discovery 393 Test Discovery Chapter 19, xUnit
Basics Patterns
Test Double 522 Test Double Chapter 23, Test
Double Patterns
Test Double 569 Variation Hard-Coded Chapter 23, Test
Class Test Double Double Patterns
Test Double 580 Variation Test-Specifi c Chapter 23, Test
Subclass Subclass Double Patterns
Test Double as 332 Variation Back Door Chapter 18, Test
Back Door Manipulation Strategy Patterns
Test Enumeration 399 Test Enumeration Chapter 19, xUnit
Basics Patterns
Test Fixture 373 Alias Testcase Class Chapter 19, xUnit
Basics Patterns
Test Fixture 644 Variation Test Helper Chapter 24, Test
Registry Organization
Patterns
Test Helper 643 Test Helper Chapter 24, Test
Organization
Patterns
Test Helper 645 Variation Test Helper Chapter 24, Test
Class Organization
Patterns
Test Helper 639 Variation Testcase Chapter 24, Test
Mixin Superclass Organization
Patterns
Test Helper 645 Variation Test Helper Chapter 24, Test
Object Organization
Patterns
Test Hook 709 Test Hook Chapter 26, Design-
for-Testability
Patterns
Test Method 348 Test Method Chapter 19, xUnit
Basics Patterns
Test Method 394 Variation Test Discovery Chapter 19, xUnit
Discovery Basics Patterns
Test Method 401 Variation Test Enumeration Chapter 19, xUnit
Enumeration Basics Patterns
Patterns, Aliases, and Variations
Patterns,
Aliases, and
Variations
Continued...
782
Name Page Relationship Base Name Chapter
Test Method 404 Variation Test Selection Chapter 19, xUnit
Selection Basics Patterns
Test Object 503 Alias Automated Chapter 22, Fixture
Registry Teardown Teardown Patterns
Test Runner 377 Test Runner Chapter 19, xUnit
Basics Patterns
Test Selection 403 Test Selection Chapter 19, xUnit
Basics Patterns
Test Spy 538 Test Spy Chapter 23, Test
Double Patterns
Test Spy 568 Alias Hard-Coded Chapter 23, Test
Test Double Double Patterns
Test Stub 529 Test Stub Chapter 23, Test
Double Patterns
Test Suite 400 Variation Test Enumeration Chapter 19, xUnit
Enumeration Basics Patterns
Test Suite 399 Alias Test Enumeration Chapter 19, xUnit
Factory Basics Patterns
Test Suite Object 387 Test Suite Object Chapter 19, xUnit
Basics Patterns
Test Suite Object 293 Variation Data-Driven Test Chapter 18, Test
Generator Strategy Patterns
Test Suite Object 293 Variation Data-Driven Test Chapter 18, Test
Simulator Strategy Patterns
Test Suite 388 Variation Test Suite Object Chapter 19, xUnit
Procedure Basics Patterns
Test Tree 380 Variation Test Runner Chapter 19, xUnit
Explorer Basics Patterns
Test Utility 599 Test Utility Chapter 24, Test
Method Method Organization
Patterns
Test Utility Test 603 Variation Test Utility Chapter 24, Test
Method Organization
Patterns
Test-Specifi c 579 Alias Test-Specifi c Chapter 23, Test
Extension Subclass Double Patterns
Test-Specifi c 579 Test-Specifi c Chapter 23, Test
Subclass Subclass Double Patterns
Appendix G Patterns, Aliases, and Variations
Patterns,
Aliases, and
Variations
783
Name Page Relationship Base Name Chapter
Testcase Class 373 Testcase Class Chapter 19, xUnit
Basics Patterns
Testcase Class 394 Variation Test Discovery Chapter 19, xUnit
Discovery Basics Patterns
Testcase Class 625 Variation Testcase Class Chapter 24, Test
per Method per Feature Organization
Patterns
Testcase Class 625 Variation Testcase Class Chapter 24, Test
per User Story per Feature Organization
Patterns
Testcase Class 404 Variation Test Selection Chapter 19, xUnit
Selection Basics Patterns
Testcase Class 388 Variation Test Suite Object Chapter 19, xUnit
Suite Basics Patterns
Testcase Class 617 Testcase Class Chapter 24, Test
per Class per Class Organization
Patterns
Testcase Class 624 Testcase Class Chapter 24, Test
per Feature per Feature Organization
Patterns
Testcase Class 631 Testcase Class Chapter 24, Test
per Fixture per Fixture Organization
Patterns
Testcase Object 382 Testcase Object Chapter 19, xUnit
Basics Patterns
Testcase 638 Testcase Chapter 24, Test
Superclass Superclass Organization
Patterns
Testing by 337 Alias Layer Test Chapter 18, Test
Layers Strategy Patterns
The xUnit 300 Variation Test Automation Chapter 18, Test
Family Framework Strategy Patterns
Transaction 668 Transaction Chapter 25, Database
Rollback Rollback Patterns
Teardown Teardown
Transient 314 Variation Fresh Fixture Chapter 18, Test
Fresh Fixture Strategy Patterns
Patterns, Aliases, and Variations
Patterns,
Aliases, and
Variations
Continued...
784
Name Page Relationship Base Name Chapter
True Humble 699 Variation Humble Object Chapter 26, Design-
Object for-Testability
Patterns
Unfi nished 494 Unfi nished Chapter 21, Result
Test Assertion Test Assertion Verifi cation Patterns
Verifi cation 477 Variation Custom Assertion Chapter 21, Result
Method Verifi cation Patterns
Appendix G Patterns, Aliases, and Variations
Patterns,
Aliases, and
Variations
785
Glossary
This glossary contains the author’s defi nitions of the terms used throughout this
book.
acceptance test
A customer test that the customer of the software plans to run to help the customer
decide whether he or she will accept the software system. Acceptance tests are usually
run manually after all automated customer tests have passed. They exercise all
layers of the system—from the user interface back to the database—and should
include any integration with other systems on which the application depends.
accessor
A method that provides access to an instance variable of an object either by
returning its value or by providing a way to set its value.
ACID
The four qualities of transactions that modern databases ensure:
• Atomic: A transaction is all or nothing.
• Consistent: All operations within a transaction see the same view of the
world.
• Independent: Transactions are independent of one another (no cross-
transaction leakage of changes).
• Durable: Once committed, the changes made within a transaction are
permanent (they don’t just vanish for no reason!).
agile method
A method of executing projects (typically, but not always, restricted to software)
that reduces the cost of change and allows customers of the software to have
more control over how much they spend and what they get for their money. Agile
Also known as:
user
acceptance
test (UAT)
786
Glossary
methods include eXtreme Programming, SCRUM, Feature-Driven Development
(FDD), and Dynamic Systems Development Method (DSDM), among many
others. A core practice of most agile methods is the use of automated unit tests.
annotation
A way of indicating something about something. JUnit version 4.0 uses annota-
tions to indicate which classes are Testcase Classes and which methods are Test
Methods; NUnit uses .NET attributes for this purpose.
anonymous inner class
An inner class in Java that is defi ned without a unique name. Anonymous inner
classes are often used when defi ning Hard-Coded Test Doubles.
anti-pattern
A pattern that shouldn’t be used because it is known to produce less than optimal
results. Code smells, or their underlying causes, are a kind of anti-pattern.
application programming interface (API)
The means by which other software can invoke some piece of functionality. In
object-oriented software, an API consists of the classes and their publicly acces-
sible methods. In procedural software, it consists of the module or package name
plus the publicly accessible procedures.
aspect-oriented programming
An advanced software modularization technique that allows improved separa-
tion of concerns by “weaving” cross-cutting concerns into code after the affected
software has been built but before it is executed.
assertion
A statement that something should be true. In xUnit-style Test Automation
Frameworks, an assertion takes the form of an Assertion Method that fails when
the actual outcome passed to it does not match the expected outcome.
787
Glossary
asynchronous test
A test that runs in a separate thread of control from the system under test (SUT)
and interacts with it using asynchronous (i.e., “real”) messages. An asynchro-
nous test must coordinate its steps with those of the SUT because this interac-
tion is not managed automatically by the runtime system. An asynchronous
test may have to include delays to give the SUT enough time to fi nish execution
before inspecting the outcome. Contrast this with a synchronous test, which
interacts with the SUT via simple method calls.
attribute
A characteristic of something. The members of the xUnit family for the .NET
languages use class and method attributes to indicate which classes are Testcase
Classes and which methods are Test Methods. The term attribute is also a syn-
onym for “instance variable” in some circles.
back door
An alternative interface to a system under test (SUT) that test software can use
to inject indirect inputs into the SUT. A database is a common example of a
back door, but it could also be any component that can be either manipulated to
return test-specifi c values or replaced by a Test Double. Contrast this with the
front door: the application programming interface (API).
BDUF
“Big design up front” is the classic “waterfall” approach to software design.
In BDUF, all requirements must be understood early in the project, and the
software is designed to support those requirements in a single design “phase.”
Contrast this with the emergent design favored by agile projects.
behavior-driven development
A variation on the test-driven development process wherein the focus of the
tests is to clearly describe the expected behavior of the system under test (SUT).
The emphasis is on Tests as Documentation rather than merely using tests for
verifi cation.
Behavior-driven development can be done using traditional members of the
xUnit family. New “members” of the family, however, have been built specifi -
cally to emphasize the change in focus. They include changes in terminology