Quantum currently depends on both mox and mock for testing. I prefer mock's lightweight approach to mock's replay-centric way of doing things, but every other project in OpenStack uses mox exclusively. In an ideal world quantum could standardize on mock and show the other projects how much better it is vs mox, but in this pragmatic world, mock probably has to go.
I'm largely to blame for this state of affairs - I wasn't familiar enough with mox's stubout module and recommended using mock to cleanly perform monkey-patching during testing for the ryu plugin. Surveying the code, I see that the nvp plugin is also using mock for testing. That is the extent of it, though. Mock is used sparingly compared to mox, and its use could easily be replaced. As much as I prefer mock, I think OpenStack projects have a responsibility to try to converge development tools and process where possible to minimize the developer knowledge necessary to be productive across projects. With that in mind, does anybody have any good arguments in favour of keeping mock? If not, I intend to file a bug that will result in mock's removal as a dependency. Thanks, Maru -- Mailing list: https://launchpad.net/~netstack Post to : netstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~netstack More help : https://help.launchpad.net/ListHelp
