Index
Prev   

Index

Symbols

${} Use markup variables to parameterise test pages
<< Use symbols to pass dynamic information
>> Use symbols to pass dynamic information

A

acceptance test
compared to unit test Automated acceptance testing
introduced Automated acceptance testing
who should write them? Who should write acceptance tests?
ActionFixture class Keep ActionFixture in mind
Args array Replace repetitive values with arguments
arguments Replace repetitive values with arguments
array
automatic conversion Better test scripts with DoFixture, Use SetUpFixture to prepare the stage for tests
automatic wrapping with DoFixture Testing lists of objects
strings or ints Working with collections
ArrayFixture Using collections directly
ArrayFixture class Testing lists of objects
compared with RowFixture Use RowFixture for better precision
converting result to test Use ArrayFixture and RowFixture to capture data batches
automated acceptance testing Automated acceptance testing
automated build tool Working in a team
scheduling tests Scheduling tests and alerts

B

Bathyscaphe Trieste Testing to prevent defects, not to find them
blank
cell Checking for errors, Use blank cells to print out results
keyword Checking for errors
BoolFixture class Writing a simple test script
BoundFixture class Binding columns to class members
bound variable Executing statements
bug, exterminating Testing to prevent defects, not to find them
business analyst
involvement in testing How does FitNesse help?, Guiding the development, Who should write acceptance tests?, Writing basic tests, Testing in plain English, Customer-friendly table
writing tests without learning wiki syntax Use blank cells to print out results
business domain object Use data-transfer objects directly, Wrapping business objects with DoFixture, Wrap existing objects for tests
business form, use as test Using existing forms for regression tables
business object Wrap existing objects for tests, Test smells
collection Testing lists of objects
FIT hooks A quick test
business rule
and acceptance test Acceptance tests should focus on business rules
and test suite Group related tests into test suites
testing directly Remove irrelevant information
testing through the UI Choosing the right thing to test

C

CamelCase
automatic conversion into links How FitNesse connects to .NET classes
valid page names FitNesse is very strict about the page names
cell operator
CompareEndsWith Load non-standard cell operators for simpler comparisons
CompareIntegralRange Load non-standard cell operators for simpler comparisons
CompareStartsWith Load non-standard cell operators for simpler comparisons
CurrencyParser Simplify verifications with a custom cell operator
loading on demand Load non-standard cell operators for simpler comparisons
non-standard Load non-standard cell operators for simpler comparisons
SubstringHandler Load non-standard cell operators for simpler comparisons
central server Using a single central server
check, keyword Use DoFixture keywords for better control, Use show and check with FitLibrary
code-oriented test FitNesse or NUnit?, Separate code-oriented and customer-oriented tests
collapsed block Include pages and use them as components
collection
automatic wrapping with DoFixture Testing lists of objects
empty Checking for empty collections
ColumnFixture class How FitNesse connects to .NET classes
inner workings Binding columns to class members
replacement when used for setup Use SetUpFixture to prepare the stage for tests
when to use ColumnFixture — the Swiss Army knife of FitNesse
Comment class Use comments to describe tables
CompareEndsWith Load non-standard cell operators for simpler comparisons
CompareEndsWith class Load non-standard cell operators for simpler comparisons
CompareIntegralRange class Load non-standard cell operators for simpler comparisons
CompareStartsWith class Load non-standard cell operators for simpler comparisons
CompareSubstring class Load non-standard cell operators for simpler comparisons
ConfigurationSetup class Load non-standard cell operators for simpler comparisons
contents, keyword Group related tests into test suites
continuous integration Integrating with automated build tools
converting test results into tests
ArrayFixture and RowFixture Use ArrayFixture and RowFixture to capture data batches
basic FIT fixtures Use blank cells to print out results
DoFixture Use show and check with FitLibrary
cross-domain scripting Setting up Selenium and Remote Control
CruiseControl.NET Integrating with automated build tools
CurrencyParser class Simplify verifications with a custom cell operator
custom data type Avoid conversions by supporting custom data types
customer
involvement in testing How does FitNesse help?, Guiding the development, Who should write acceptance tests?, Writing basic tests, Testing in plain English
-oriented test FitNesse or NUnit?, Automated acceptance testing, Separate code-oriented and customer-oriented tests
error checking Checking for errors
custom fixture class Implement domain-specific tests using custom fixtures

D

DatabaseEnvironment class Connecting in standalone mode
DatabaseTest class Connecting to the database
database testing Testing database code
data-transfer object Use data-transfer objects directly, Wrapping business objects with DoFixture, Wrap existing objects for tests
data type
and cell operators Simplify verifications with a custom cell operator
custom Avoid conversions by supporting custom data types
handling Handling data types
matching Cell operators
DbFit Testing database code
debugging tests Attaching the Visual Studio debugger
DecimalFixture class Writing a simple test script
dedicated server, Selenium Running tests on a remote server
define, keyword Use markup variables to parameterise test pages
dependency injection Embed fixtures for best results
describe-demonstrate-develop Automated acceptance testing
DoCell method Executing tables
DoCells method Executing tables
DoFixture class
automatic collection wrapping Testing lists of objects
embedding other fixtures Embed fixtures for best results
introduced Better test scripts with DoFixture
wrapping business objects Wrapping business objects with DoFixture
DoRow method Executing tables
DoRows method Executing tables
DoTable method Executing tables
DoTables method Executing tables
DoubleFixture class Writing a simple test script
draw pool Lottery rules
DTO (see data-transfer object)
duplication, removing Removing duplication
dynamic information Use symbols to pass dynamic information

E

empty collection Checking for empty collections
error, keyword Checking for errors
example
CurrencyParser Simplify verifications with a custom cell operator
HelloWorld A quick test
invoice Using existing forms for regression tables
Excel
converting from Using existing forms for regression tables
writing tests Use blank cells to print out results
exception, keyword Checking for errors
exec, NAnt task Running tests with NAnt
executable specification Automated acceptance testing
Execute class Executing statements
ExecuteException class Cell operators
ExecuteProcedure class Working with stored procedures
expected outcome How FitNesse connects to .NET classes
Export class Connecting in standalone mode
exterminating bugs Testing to prevent defects, not to find them

F

face-saving tests Face-saving tests
fail, keyword Checking for errors
field name How FitNesse connects to .NET classes
files, organising Organising the files
FIT
inner workings What really happens during a test?
introduced Getting FIT
fit.dll A quick test
FitLibrary ColumnFixture — the Swiss Army knife of FitNesse, Better test scripts with DoFixture
FitNesse
as a Windows service Organising the files
benefits How does FitNesse help?
compared to NUnit FitNesse or NUnit?
connecting to .NET classes How FitNesse connects to .NET classes
download Installing FitNesse
inner workings What really happens during a test?
installation Installing FitNesse
internal version control Using a single central server
introduced Getting FIT
security Using a single central server
fitnesse.jar Setting up FitNesse
FitNesseRoot directory Start with a fresh wiki
fitsharp.dll A quick test
fixture
ActionFixture Keep ActionFixture in mind
arguments Replace repetitive values with arguments
ArrayFixture Testing lists of objects
BoolFixture Writing a simple test script
BoundFixture Binding columns to class members
ColumnFixture How FitNesse connects to .NET classes
Comment Use comments to describe tables
coordinating Coordinating fixtures
custom implementation Implement domain-specific tests using custom fixtures
DatabaseEnvironment Connecting in standalone mode
DatabaseTest Connecting to the database
DecimalFixture Writing a simple test script
DoFixture Better test scripts with DoFixture
DoubleFixture Writing a simple test script
embedding Embed fixtures for best results
Execute Executing statements
ExecuteProcedure Working with stored procedures
Export Connecting in standalone mode
FloatFixture Writing a simple test script
import Import namespaces and clean up table headers
inner structure Executing tables
Insert Preparing test data
IntFixture Writing a simple test script
LongFixture Writing a simple test script
Query Verifying query results
RowFixture Use RowFixture for better precision
SequenceFixture Use SetUpFixture to prepare the stage for tests
SetUpFixture Use SetUpFixture to prepare the stage for tests
SqlServerTest Connecting in flow mode
StringFixture Writing a simple test script
TableFixture Using existing forms for regression tables
target object Use data-transfer objects directly
WebTest Starting and stopping the browser
Fixture class A quick test, ColumnFixture — the Swiss Army knife of FitNesse
FloatFixture class Writing a simple test script
flow Embed fixtures for best results
and class names Use SetUpFixture to prepare the stage for tests
and import Settlement tests in flow mode
and SequenceFixture Use SetUpFixture to prepare the stage for tests
DbFit database connection Connecting in flow mode
DbFit mode Connecting to the database
how DoFixture takes over Executing tables
with test suites Create test suites in flow mode
flow mode Using collections directly
FolderRunner What really happens during a test?
form, use as test Using existing forms for regression tables
Framework for Integrated Testing (see FIT)

G

GetTargetObject method Use data-transfer objects directly, Wrap existing objects for tests

H

HelloWorld A quick test

I

IDraw interface Writing efficient test scripts
IDrawManager interface Writing efficient test scripts
IEnumerable interface, automatic wrapping with DoFixture Testing lists of objects
import Import namespaces and clean up table headers
and flow mode Settlement tests in flow mode
cancelling Connecting in standalone mode
include directive Include pages and use them as components
Insert class Preparing test data
installing FitNesse Installing FitNesse
instsrv.exe Organising the files
IntFixture class Writing a simple test script
invariant on the code Covering legacy code with tests
IPlayerManager interface Writing simple test scripts, Writing efficient test scripts
IPlayerRegistrationInfo interface Writing simple test scripts
ISelenium interface Using ISelenium
ITicket interface Writing efficient test scripts

K

keyword
blank Checking for errors
check Use DoFixture keywords for better control, Use show and check with FitLibrary
contents Group related tests into test suites
define Use markup variables to parameterise test pages
error Checking for errors
exception Checking for errors
fail Checking for errors
include Include pages and use them as components
missing Testing lists of objects
name Using named fixtures
no Writing a simple test script
not Use DoFixture keywords for better control
note Use DoFixture keywords for better control
null Checking for errors
path How FitNesse connects to .NET classes, Organising the files
reject Use DoFixture keywords for better control
show Use DoFixture keywords for better control, Use show and check with FitLibrary
surplus Testing lists of objects
use Using named fixtures
with Setting the system under test from FitNesse
yes Writing a simple test script

L

legacy code Testing legacy code
LongFixture class Writing a simple test script
lottery rules Lottery rules

M

markup variables Use markup variables to parameterise test pages
merge, CruiseControl.NET block Integrating FitNesse with CruiseControl.NET
method name How FitNesse connects to .NET classes
and DoFixture Better test scripts with DoFixture
and SequenceFixture Use SetUpFixture to prepare the stage for tests
missing, keyword Testing lists of objects
mistake-proofing Testing to prevent defects, not to find them
multi-step test Writing simple test scripts
mySystemUnderTest Wrapping business objects with DoFixture
mySystemUnderTest property Wrap existing objects for tests

N

name
keyword Using named fixtures
NAnt Running tests with NAnt
.NET 2 test runner
making default Configure FitNesse to run .NET tests by default
.NET formatting Use .NET formatting to make values easier to read
.NET 2 test runner
installing Installing FitNesse
no, keyword Writing a simple test script
not, keyword Use DoFixture keywords for better control
note, keyword Use DoFixture keywords for better control
null, keyword Checking for errors
NUnit Beyond unit tests, Testing in plain English
compared to FitNesse FitNesse or NUnit?
equivalent code to ColumnFixture How FitNesse connects to .NET classes

P

PageFooter Defining common actions
PageHeader Defining common actions
page property
remote wiki URL Importing tests from a remote wiki
suite Group related tests into test suites
test A quick test
parameterised test page Writing a simple test script, Use markup variables to parameterise test pages
Parse
class The parse tree
method Handling data types, Avoid conversions by supporting custom data types
Parse method Beware of test extensions
ParseSymbol class Cell operators
parse tree The parse tree
path, keyword How FitNesse connects to .NET classes, Organising the files
payout pool Lottery rules
PlayerManager class Writing simple test scripts
Poka-Yoke Testing to prevent defects, not to find them
ProcessTables method Executing tables
property name How FitNesse connects to .NET classes
public field ColumnFixture — the Swiss Army knife of FitNesse
publishers, CruiseControl.NET block Integrating FitNesse with CruiseControl.NET

Q

Query class Verifying query results
quick test Don't mix quick and slow tests

R

Recall method Use data-transfer objects directly
red-green-refactor Guiding the development
reflection, DLL deployment Organising the files
regression test Manageable larger tests: use FitNesse
reject, keyword Use DoFixture keywords for better control
remote server, Selenium Running tests on a remote server
remote wiki Importing tests from a remote wiki
Reset Changing the system under test
root page Defining common actions
running .NET by default Configure FitNesse to run .NET tests by default
RowFixture class Use RowFixture for better precision
converting result to test Use ArrayFixture and RowFixture to capture data batches
for databases Verifying query results
Runner.exe How FitNesse connects to .NET classes
stopping tests Attaching the Visual Studio debugger

S

scheduling tests Scheduling tests and alerts
security of FitNesse Using a single central server
Selenium
integrating with FitNesse Connecting from FitNesse
introduced Introducing Selenium
looking for HTML element Simulating client interaction
on a dedicated server Running tests on a remote server
opening a URL Simulating client interaction
Remote Control Introducing Selenium
starting the browser Starting and stopping the browser
stopping the browser Starting and stopping the browser
SequenceFixture class Use SetUpFixture to prepare the stage for tests
serialisation, DLL deployment Organising the files
session control test Workflow and session control
SetFixture class Use RowFixture for better precision
SetSystemUnderTest System under test with ColumnFixtures
SetUp Group related tests into test suites
in flow mode Create test suites in flow mode
setup fixture Use setup fixtures to store static context
SetUpFixture class Use SetUpFixture to prepare the stage for tests
for databases Preparing test data
show, keyword Use DoFixture keywords for better control, Use show and check with FitLibrary
singleton Use symbols to pass dynamic information
slow test Don't mix quick and slow tests
special page
PageFooter Defining common actions
PageHeader Defining common actions
root Defining common actions, Configure FitNesse to run .NET tests by default
SetUp Group related tests into test suites, Create test suites in flow mode
SuiteSetUp Defining common actions
SuiteTearDown Defining common actions
TearDown Defining common actions, Create test suites in flow mode
Spreadsheet to FitNesse Use blank cells to print out results
SqlServerTest class Connecting in flow mode
srvany.exe Organising the files
stopping tests Attaching the Visual Studio debugger
stored procedures Working with stored procedures
story test Guiding the development
StringFixture class Writing a simple test script
subwiki Group related tests into test suites
in flow mode Create test suites in flow mode
links Links within a subwiki
SuiteSetUp Defining common actions
SuiteTearDown Defining common actions
surplus, keyword Testing lists of objects
symbol Use symbols to pass dynamic information
accessing from code Use data-transfer objects directly
as argument Use data-transfer objects directly
implementation Cell operators
in output columns Using symbols to check dynamic values
standard access classes Writing a simple test script
symbolic links Reuse entire suites with symbolic links
system under test Wrapping business objects with DoFixture, Wrap existing objects for tests

T

table
as test description How FitNesse connects to .NET classes
passing values between Passing values between tables
TableFixture class Using existing forms for regression tables
table of contents
for a subwiki Group related tests into test suites
target object Use data-transfer objects directly, Wrap existing objects for tests
compared to system under test Wrapping business objects with DoFixture
tasks, CruiseControl.NET block Integrating FitNesse with CruiseControl.NET
TDD (see test-driven development)
team working
building shared understanding Introduction
passing on requirements How does FitNesse help?
setup options Working in a team
TearDown Defining common actions
in flow mode Create test suites in flow mode
test, multi-step Writing simple test scripts
test-driven development
benefits Why bother with TDD?
three rules Guiding the development
test extension Remove irrelevant information, Beware of test extensions, Test smells
test page A quick test
converting to test suite Group related tests into test suites
hiding parts Hide parts of the page
include pages as components Include pages and use them as components
linking Don't forget the test
links Links within a subwiki
parameterised Writing a simple test script, Use markup variables to parameterise test pages
symbolic links Reuse entire suites with symbolic links
valid names FitNesse is very strict about the page names
TestRunner Using TestRunner
test runner
.NET by default Configure FitNesse to run .NET tests by default
FolderRunner What really happens during a test?
Runner.exe How FitNesse connects to .NET classes
TestRunner Using TestRunner
test script Writing simple test scripts
test smell Removing duplication, Test smells
test stub Better test scripts with DoFixture
test suite Group related tests into test suites
in flow mode Create test suites in flow mode
three rules of TDD Guiding the development
Toyota Testing to prevent defects, not to find them
troubleshooting
with DoFixture Use DoFixture keywords for better control
with Selenium A quick Selenium example
with Visual Studio Attaching the Visual Studio debugger

U

UI (see user interface, testing)
unit test
compared to acceptance test Automated acceptance testing
rules by Michael Feathers Quick basic tests: use NUnit
tool abuse Beyond unit tests
unstable test Testing legacy code
usability constraint Choosing the right thing to test
use
keyword Using named fixtures
use case
compared to user stories Guiding the development
user interface, testing Testing web interfaces
user story Guiding the development
compared to use cases Guiding the development
introduced Guiding the development
selected Selected user stories

V

version control
external Storing tests in a version control system
internal Using a single central server, Storing tests in a version control system
Visual Studio
debugging fixtures Attaching the Visual Studio debugger
deploying DLLs Organising the files

W

WaitForPageToLoad method Inspecting results
web interface, testing Testing web interfaces
WebTest class Starting and stopping the browser
wiki A quick test
import Importing tests from a remote wiki
new Start with a fresh wiki
Windows resource kit Organising the files
Windows service Organising the files
WinningsCalculator class Writing basic tests
with
keyword Setting the system under test from FitNesse
Word
converting from Using existing forms for regression tables
writing tests Use blank cells to print out results
workflow Remove irrelevant information
fixtures Executing tables
rule Choosing the right thing to test
test Workflow and session control

Y

yes, keyword Writing a simple test script

Z

zero quality control Testing to prevent defects, not to find them
ZQC (see zero quality control)
Prev   
Web code Home