Comment 3 for bug 1623573

Matt, basically it would be similar to how the existing gabbi fixtures start and stop the database: they borrow code from the fixtures in nova/tests/fixtures.py but drive them more explicitly rather than letting them be fixtures in the Fixtures (the class) kinds of things.

So, yeah, in the APIFixture (since every gabbit loads that one).

Gabbi fixtures are context managers that surround the entire yaml file, so if we add stderr and stdout capturing, it will capture for the entire file before producing any output.

It won't look like what's happening in nova.test but ought to do the same thing.