Glance

Use unittest2 and refactor some DRY problems in tests

Registered by Jay Pipes

We should use unittest2 features, including @skipIf and the setUpClass @classmethods. SQLAlchemy already requires unittest2, so it's not a new dependency for us.

In addition, we should clean up some of the repetitive code shared between /tests/functional/test_curl_api.py and /tests/functional/test_s3.py

In addition, we should be able to rework the unit testing to remove the need for a faked datastore. We should be able to just force a SQLite in-memory database, which should add the DB API layer into the unit testing mix.

Blueprint information

Status:
Complete
Approver:
Jay Pipes
Priority:
Low
Drafter:
Jay Pipes
Direction:
Approved
Assignee:
Jay Pipes
Definition:
Approved
Series goal:
Accepted for diablo
Implementation:
Implemented
Milestone target:
milestone icon 2011.3
Started by
Jay Pipes
Completed by
Jay Pipes

Related branches

Sprints

Whiteboard

First appeared in diablo-4

Work Items:

[bcwaldon] Remove redundant cURL tests: DONE
[jaypipes] Remove faked out data store (https://review.openstack.org/184): DONE
[jshepherd] Use unittest2, @skipIf and setUpClass (https://review.openstack.org/#change,148): DONE
[jaypipes] Use httplib2 functional test in S3 functional test case (https://review.openstack.org/180): DONE
[jaypipes] Create a Swift functional test case (https://review.openstack.org/#change,180): DONE

(?)

Work Items

Nearby

This blueprint contains Public information 
Everyone can see this information.