Tag Archives: atdd

Agile '06 Workshop: Example-Based Specifications

Posted on August 31, 2006 by Bill Wake

Exploring example-based specifications. Continue reading →

Tagged , , ,

Extreme Test Makeover – Agile ’06

Posted on July 26, 2006 by Bill Wake

Lessons for Fit. Continue reading →

Tagged , , ,

Review – Fit for Developing Software

Posted on July 8, 2005 by Bill Wake

Review of “Fit for Developing Software” by Mugridge and Cunningham. Continue reading →

Tagged , , ,

Fit Reading (Part 8 of 8) – RowFixture

Posted on June 25, 2005 by Bill Wake

Fit code, part 8, RowFixture. Continue reading →

Tagged ,

Fit Reading (Part 7 of 8) – ColumnFixture

Posted on June 24, 2005 by Bill Wake

Fit part 7, ColumnFixture. Continue reading →

Tagged ,

Semantics of Fit: A Path Toward New Tools

Posted on June 18, 2005 by Bill Wake

Fit’s standard interpretation tells us how well a program does against a set of test cases. We can design new semantics for reporters (that give us interesting information) and for rewriters (that make interesting transformations of our tests). Continue reading →

Tagged , , , ,

Fit Reading (Part 6 of 8) – TypeAdapter

Posted on June 14, 2005 by Bill Wake

Fit code, part 6 – TypeAdapter. Continue reading →

Tagged ,

Fit Reading (Part 5 of 8) – ActionFixture

Posted on June 13, 2005 by Bill Wake

Fit code, part 5 – ActionFixture. Continue reading →

Tagged ,

Fit Reading (Part 4 of 8) – Fixture

Posted on June 3, 2005 by Bill Wake

Fit code, part 4 – Fixtures. Continue reading →

Tagged ,

Fit Reading (part 3 of 8) – Parse and Fixture

Posted on June 2, 2005 by Bill Wake

Fit code, part 3. Continue reading →

Tagged ,

Fit Reading (Part 2 of 8)

Posted on June 1, 2005 by Bill Wake

Fit’s code, part 2. Continue reading →

Tagged ,

Fit Reading (part 1 of 8)

Posted on May 30, 2005 by Bill Wake

A tour of Fit’s code. Continue reading →

Tagged ,

Procedural and Declarative Tests

Posted on March 1, 2005 by Bill Wake

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 →

Tagged , , ,

Tools – Especially JUnit and Fit

Posted on December 25, 2003 by Bill Wake

JUnit is a tool for unit testing; Fit is a tool for system testing. Continue reading →

Tagged , ,

Fit Spreadsheet – Output

Posted on April 20, 2003 by Bill Wake

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 →

Tagged , , ,