Fix test directory location

How about putting in an __init__.py so you can import keystone.test?

You already have an `__init__.py` in there; which is actually what causes the `import test` ambiguities.

Another option, which seems more recommended by Pythonistas out there, is have all your tests (or at least the unit tests) at `<project>/test`. In Swift, we also have functional and probe tests, so I'm not sure what the team will decide. Maybe a `<project>/test`, `<project>/functest`, and `<project>/probetest` or something.

To show the problem, here's a run down on a fresh system:

    # First, just grab the source repos
    $ mkdir ~/example
    $ git clone <email address hidden>:gholt/keystone.git ~/example/keystone-repo
    $ bzr branch lp:swift ~/example/swift-repo

    # This shows that python comes with its own test package.
    $ cd ~ ; python -c 'import test ; print test'
    <module 'test' from '/usr/lib/python2.6/test/__init__.pyc'>

    # But now, once we install keystone for development, it takes over the new # test package.
    $ cd ~/example/keystone-repo ; sudo python setup.py develop
    $ cd ~ ; python -c 'import test ; print test'
    <module 'test' from '/home/gholt/example/keystone-repo/test/__init__.py'>

    # In this case, installing swift for development means it ends up with # keystone's test package.
    $ cd ~/example/swift-repo ; sudo python setup.py develop
    $ cd ~ ; python -c 'import test ; print test'
    <module 'test' from '/home/gholt/example/keystone-repo/test/__init__.pyc'>

    # If I remove keystone, swift now gets the test package.
    $ cd ~/example/keystone-repo ; sudo python setup.py develop -u
    $ cd ~ ; python -c 'import test ; print test'
    <module 'test' from '/home/gholt/example/swift-repo/test/__init__.py'>

    # If I remove swift, now we're back to way the things should've been.
    $ cd ~/example/swift-repo ; sudo python setup.py develop -u
    $ cd ~ ; python -c 'import test ; print test'
    <module 'test' from '/usr/lib/python2.6/test/__init__.pyc'>

Fixed. I'm not sure what to do with the tools folder though. Any elegant suggestions? Maybe wait for openstack-common...

Ah, I'm not sure on tools. Actually, I'm still not sure on tests either, but when you have a nice small project you can make these changes quickly. :)

I think I'm going to do even more searching, probably make an annoying blog post, and see what settles out of all that.

http://tlohg.com/python-test-placement