Replace `>>` with `in` and make some `val`s lazy, to no avail
Replace `>>` with `in` and make some `val`s lazy, to no avail

This makes example fragments run in the correct order, in a small test spec,
with perhaps 10 - 20 tests.  (From top to bottom, that is.) Instead of running
them in some random order.  Specs2 runs tests in some weird random order, if
some of them has side effects. No idea why. Specs 1 didn't behave like that.
(And I *did* specify `sequential`.)

This doesn't mend DaoTckTest though. Tests still run in random order, and
Specs2 completely ignores all `step(...)`s that supposedly always always run
before subsequent test fragments. I'm giving up. I'll port to ScalaTest
instead.  ScalaTest seems easier to use, I've read the docs.

debiki/debiki-server-old,debiki/debiki-server-old,debiki/debiki-server-old,debiki/debiki-server-old