Fit Reading (part 3 of 8) – Parse and Fixture
Fit code, part 3. Continue reading Fit Reading (part 3 of 8) – Parse and Fixture
Exploring Extreme Programming
Fit code, part 3. Continue reading Fit Reading (part 3 of 8) – Parse and Fixture
Fit’s code, part 2. Continue reading Fit Reading (Part 2 of 8)
A tour of Fit’s code. Continue reading Fit Reading (part 1 of 8)
Procedural tests focus on a series of steps; declarative tests work from the input and states. Procedural tests are natural to write, but consider whether a declarative test expresses your intent more concisely and clearly. Continue reading Procedural and Declarative Tests
JUnit is a tool for unit testing; Fit is a tool for system testing. Continue reading Tools – Especially JUnit and Fit
Starting Fit To use fit, you create a web page that has tables in it; the tables specify tests. (There are other options but that is easiest.) In this case, I’m using Microsoft Word™ and saving the file in HTML Continue reading Fit Spreadsheet – Output
Ward Cunningham has created an acceptance testing framework known as fit. (See http://fit.c2.com for more details.) In this brief experiment, we’ll use tests to help specify a simple spreadsheet for strings. Continue reading Fit Spreadsheet
Tests for a(n imaginary) library query system. Continue reading Acceptance Tests for a Query System
An acceptance test is a test that the user defines, to tell whether the system as a whole works the way the user expects. Ideally, the acceptance tests are defined before the code that implements the feature. Acceptance tests are Continue reading Acceptance Test Mechanisms