I've switched on the Z3 test runners timing mechanism. An initial score is that the main launchpad tests take 9 minutes to run, which indicates that:
a) The Z3 test runners timing mechanism isn't counting setup/teardown time
b) Most of our time is spent doing setup/teardown
As the Z3 functional framework is cached and cannot be torn down, the setup/teardown that is hurting us would be the postgresql fixture and to a lesser extent the librarian.
I've switched on the Z3 test runners timing mechanism. An initial score is that the main launchpad tests take 9 minutes to run, which indicates that:
a) The Z3 test runners timing mechanism isn't counting setup/teardown time
b) Most of our time is spent doing setup/teardown
As the Z3 functional framework is cached and cannot be torn down, the setup/teardown that is hurting us would be the postgresql fixture and to a lesser extent the librarian.