scenarios for aggregates and value objects
very rough cut of a Middleware testing scenario
massive reorg
prepping for printable specifications
Merge branch 'master' into cedar-testing
example code on how to use the Scenario DSL
need to pass the ar id all the way down
slight api change

making sure failing tests fail
cleanup
must throw a scenario exception so the runner can deal
<sigh>
oops
basic printing
don't like passing in the writer into the method

scenario result should know if it passed or not
recording test duration
should support flushing
let the printer decide how it wants to print
now with teamcity support!

possible race condition in test runner. a better developer should probably look at this
that was an interesting failure
work around for Action/Func/Task weirdness

compiler will not convert an Expression<Action<T>> to Expression<Func<T, Task>>