Screen-Based Tests: Two Extremes Screen-based tests focus on what’s visible rather than internal representations. We’ll consider two extremes for testing screen-based output: fully manual and fully automated. Then we’ll look at moves that can help you evolve from one to Continue reading Screen-Based Tests: Testing Graphics, Part 3
Oracles are things that can tell us whether or not a result is correct. For some tests, an oracle is as simple as comparing a couple strings or numbers. Other tests have many acceptable results and it’s harder to know what’s right. I Continue reading Testing with Simple and Combinatorial Oracles
T is for Testable in the INVEST model. A testable story is one for which, given any inputs, we can agree on the expected system behavior and/or outputs.
Schools of Software Testing. Continue reading Schools of Software Testing (Pettichord)
Lessons for Fit. Continue reading Extreme Test Makeover – Agile ’06
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 Semantics of Fit: A Path Toward New Tools
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