Bug 1041816

Summary:	[RFE][glance]: Improve functional tests
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	RFEs	Assignee:	RHOS Maint <rhos-maint>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	markmc, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/glance/+spec/refactoring-better-faster-stronger-functional-tests
Whiteboard:	upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-19 17:42:50 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description RHOS Integration 2013-12-12 19:27:50 UTC

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