Simplify acceptance tests for new Flocker driver

[shay-berman]

Since there are tests in the acceptance tests that not really related for testing a new Flocker driver. (for example test_export which is not relevant for the flocker driver),

So please consider to split the acceptance tests into two different parts, one for Flocker Project acceptance tests and one for new Flocker driver acceptance tests.

The motivation is just to simplify the acceptance tests process for new Flocker drivers (mainly to reduce the tests run time for irrelevant tests).

Thanks

[wallrj]

Thanks for reporting @shay-berman

The simplest thing we could do would be to change the documentation at https://flocker-docs.clusterhq.com/en/latest/gettinginvolved/plugins/building-driver.html#certifying-your-driver to say exactly which tests we expect to pass.

E.g.

./admin/run-acceptance-tests --provider managed ... -- flocker.acceptance.endtoend.test_dataset

...is probably sufficient.