Cloned from launchpad blueprint https://blueprints.launchpad.net/glance/+spec/refactoring-better-faster-stronger-functional-tests.

Description:

Functional tests in glance run the glance api and registry servers in separate processes. This causes a number of problems:

- race conditions around port selection
- other unknown sources of indeterminacy
- slowness
- process logs are hidden away or lost, so there are difficulties when debugging
- dead processes are left around in certain failure scenarios

Each of these items can be addressed individually. But under the aegis of this blueprint, I propose that we simply stop functionally testing at the process level, and instead test some slightly smaller but almost equivalent abstraction that can be managed in the same process as the test runner (say, at the wsgi app level).

Specification URL (additional information):

None