delta/openstack/taskflow.git/taskflow/tests/unit/persistence, branch 0.6.0

Move over to using oslo.utils [reflection, uuidutils]

2014-12-18T21:55:41+00:00

The reflection module is now part of oslo.utils so we should
remove our local version and use that version instead; this
also goes for the uuidutils module which is now part of
oslo.utils as well so we no longer need our local version
copied from the incubator...

Note that one reflection method `find_subclasses` which was to
specific to taskflow is now moved to the misc utility module
instead of its prior home in the reflection module.

Change-Id: I069881c80b0b2916cc0c414992b80171f7eeb79f

Merge "Fix split on "+" for connection strings that specify dialects"

2014-12-15T19:57:35+00:00

Fix split on "+" for connection strings that specify dialects

2014-12-05T00:59:54+00:00

Fixes bug 1399486

Change-Id: I3b7e6331751f25d9c4221393e8329934925791e7

Ensure that the zookeeper backend creates missing atoms

2014-11-24T18:06:02+00:00

When 'create_missing' is true the atom should be created
instead of raising an exception; this is used when a flow
detail is updated with a new detail and then saved.

This also adds test cases that verify this happens so that
we verify this on an ongoing basis.

Fixes bug 1395812

Change-Id: I4851a08ff1ab4101dbec4a6656177908095c3c52

Remove direct usage of the deprecated failure location

2014-10-21T22:37:44+00:00

Internally we should be using the new location and not the
deprecated location wherever possible. This avoids emitting
warnings messages on our own code, which is a dirty habit.

Change-Id: Idac5a772eca7529d92542ada3be1cea092880e25

Switch to a custom NotImplementedError derivative

2014-10-08T22:36:03+00:00

When a feature or method is not implemented it's useful
to throw our own derivative of a NotImplementedError error
so that we can distingush these types of errors vs actual
usage of NotImplementedError which could be thrown from
driver or user code.

Change-Id: I8d5dfb56a254f315c5509dc600a078cfef2dde0b

Remove db locks and use random db names for tests

2014-08-12T20:23:22+00:00

Removed database locks against the database openstack_citest and
implemented random name generation for new databases created just
for persistence testing.
Once the locks were removed, using 'template1' as the initial db
for postgres connections was problematic, because postgres refuses
to create databases when there are multiple connections to
'template1'.  Switched to using 'postgres' as an initial db to use.
Changed _reset_database to _init_db since we are always working
with a brand new database, and removed the 'drop database' before
a 'create database.
Added a _remove_db method to remove the database once testing was
finished.

Change-Id: Iaf1c101df9c268da48db7432bcbc0467f6486bcd
Closes-Bug: 1327469

Enabled hacking checks H305 and H307

2014-07-17T07:05:48+00:00

* H305  imports not grouped correctly
* H307  like imports should be grouped together

Change-Id: If1dd9c89f65ede6959865a885777cb08c263eca0

Fix traces left in zookeeper

2014-06-27T22:29:22+00:00

We currently are leaving the root node in zookeeper
whenever this test is ran, we should instead be removing
the full directory and any children to avoid leaving
test data behind in zookeeper (aka, cleanup our dirty
laundry).

Fixes bug 1330807

Change-Id: I56d9dabd9926463506e1710ddf0a6c4831d5dc57

Upgrade hacking version and fix some of the issues

2014-06-14T02:27:17+00:00

Update hacking to the new requirements version and
fix about half of the new reported issues. The other
hacking issues are for now ignored until fixed by
adjusting our tox.ini file.

This commit fixes the following new hacking errors:

H405 - multi line docstring summary not separated
       with an empty line
E265 - block comment should start with '# '
F402 - import 'endpoint' from line 21 shadowed by
       loop variable

Change-Id: I6bae61591fb988cc17fa79e21cb5f1508d22781c