Can't run tests in development without first running a few steps
With merging  and , you can no longer just run tests in development. You have to first perform a couple steps like generating and installing the bindings. We either need docs and/or an alias that will take care of generating/installing the bindings, setting up the fixture container, etc.
if the plugin is specified on pulp_install_plugins, bindings will be automatically generated https://github.com/pulp/ansible-pulp/blob/master/roles/pulp-devel/tasks/bashrc.yml#L36-L43
I was thinking we could have the tests generate the bindings themselves as a pre-test step. Then when running any number of tests, it builds the bindings as the first step and then uses them for the duration of the test run.
This would allow us to receive this feature in the develpoment environment, on travis and github CI's, and downstream packagers too. When packaging Pulp for say Debian, you want to apply a limited number of upstream patches and you need to run the tests when you do.
Please register to edit this issue