Decide how to supply valid test data

I thought this series had a lot of great ideas on default data and writing less brittle tests: http://www.cheezyworld.com/2010/11/21/ui-tests-default-dat/ In this entry and the related posts, @chzy puts forth the strategy of abstracting so that the tests do break when things change but that a minimum amount of work is required to update their code.

What I discovered was that for the vast majority of Scenarios the actual data requirements that were specific to the thing we were testing was very small. And yet sometimes the amount of data needed to complete the scenario was fairly high. What I needed was a way to have the system provide default data for everything that was not specific to the scenario and yet allow me to override any default data that had to be exact for the test.

jhedstrom has implemented drush as a way to set up and teardown user data. We can't use that with Drupal.org as-is since they've dropped the access column from the database, so this, and writing tests for authenticated users, is currently blocked.

sdboyer made changes to drush on git6site that allow this to work, so marking this fixed.