Be consistent on test tools and drivers

[Dave McCowan]

Most of the time Barbican uses testr to run unit tests and functional tests.
   functionaltests/run_tests.sh
   tox -e py27

In one case Barbican uses nosetests
   tox -e functional

It would be better to use one tool for all.

One reason is test attributes. Nose only knows about nose attributes. Testr only knows about testtools attributes.
To benefit from using attributes, we need to pick one flavor.

One good use of test attributes is to mark those tests that can not be run in parallel with a tag such as "no_parallel", then when running tests only run those tests not marked so with the --parallel parameter.

[Fernando Diaz (diazjf)]

Fix available here:
https://review.openstack.org/#/c/218117/

[Kaitlin Farr (kaitlin-farr)]

@diazjf, just a small note, I think the "In Progress" means you're working on it, "Fix Committed" means that patch has been merged, "Fix released" means that the latest release of the project includes your fix.

[Fernando Diaz (diazjf)]

^^ I'll keep that in mind, Thanks Kaitlin.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/218117
Committed: https://git.openstack.org/cgit/openstack/barbican/commit/?id=e67ca803b9e4c53f3ce81fb835ca22a5df8f5fef
Submitter: Jenkins
Branch: master

commit e67ca803b9e4c53f3ce81fb835ca22a5df8f5fef
Author: Fernando Diaz <email address hidden>
Date: Fri Aug 28 01:38:39 2015 -0500

    Use testr for running functional tests and documentation

    Alters tox.ini to use testr rather than nosetests.
    Also, adds documentation on how to use tox to run a
    single functional test class.

    Change-Id: I1333ead397f338ee3da3d81b0e1de8e93283a2b5
    Closes-Bug: #1490747