The buildmaster tests rely on bringing up a slave. If we're going to separate launchpad-buildd from Launchpad, we need to either:
- make it bring up the slave, by running a separately-installed slave
- not have any code-level tests that rely on starting an actual slave, and count on testing that during integration
The former seems better.
So we possibly want a separate launchpad-buildd-fixtures package. For the moment I'll just try to get the tests to work in-tree, but not duplicated.
The buildmaster tests rely on bringing up a slave. If we're going to separate launchpad-buildd from Launchpad, we need to either: installed slave
- make it bring up the slave, by running a separately-
- not have any code-level tests that rely on starting an actual slave, and count on testing that during integration
The former seems better.
So we possibly want a separate launchpad- buildd- fixtures package. For the moment I'll just try to get the tests to work in-tree, but not duplicated.