bin/cinder-* scripts are not unit tested

[Eric Harney]

We should add something that does at least basic testing on bin/cinder-{all, api, backup, manage, rtstool, scheduler, volume} to prevent issues like the one fixed in https://review.openstack.org/#/c/79791/ from slipping through.

[Eric Harney (eharney)]

I suspect that part of this should be moving to entry points for most of the code in these scripts. I looked at this some time ago in https://review.openstack.org/#/c/52229/ which can be used as an example.

[Thang Pham (thang-pham)]

This looks like a big change.

After reading what John Griffith posted in the review, I will start a cinder-specs and blueprint to track this and get it approve. I understand that the reason behind the change is to use pbr to setup the correct console scripts that will call the main function in cinder.cmd. It will allow us to import from cinder.cmd and individually test each command. I see that nova and glance does a similar thing.

Is there anything else (other than the reasons above) that I should include in the cinder-specs?

[Thang Pham (thang-pham)]

The blueprint for this has been added and is pending review: https://blueprints.launchpad.net/cinder/+spec/unit-test-cases-for-cinder-scripts