modified from Greg Gagne's Agile.EDU presentation:
*   example format for Acceptance Tests

*   remember: acceptance tests are "higher-level" than
    unit tests;

    *   acceptance tests specify conditions that must be
        met for a user story to be satisfied
	(to show that your iteration is satisfying
	that user story)

*   you could make a chart for one or more
    acceptance tests:

    *   note: a good acceptance test (really, any type of
        test) is reasonably REPEATABLE,
	and such that "anyone" could perform the test
	and tell if it succeeds

    *   probably should include a space for the date
        a test was done

    *   you could have a test #
    *   user story it covers (can give its short name)
    *   preconditions
        e.g.,
	"The program is open at the login screen"

    *   test actions (listed specifically and
        "repeatably")
        *   for example:
	    *   enter admin login "admintest" in the user
	        name textbox

	    *   enter admin password "admintest" in
	        the user password textbox

	    *   click submit button

    *   expected outcome <-- a test is not a test
        if you don't know what SHOULD happen!
        *    for example,
	     "the administrator home screen should
	     display"

    *   actual outcome <-- did the test pass?
        *   and a space to somehow record that

    *   note that a single user story may need
        several acceptance test cases to test it --
	a login user story should include what happens
	for a "good" login (one test case)
	and a "bad" login (another test case)

*   goal:
    a client would look at a set of acceptance test
    cases for a user story,
    and readily agree that those acceptance test
    cases passing WOULD show that that user story
    had been successfully implemented;