That could also work, another problem is that many times when I am debugging
using tests I will use something like pbd. In this case we will always need
a way to fall back to the single thread mode.
On Jan 15, 2010 2:38 AM, "Russell Keith-Magee"
wrote:
On Fri, Jan 15, 2010 at 9:59 AM, Vitaly Bab
On Fri, Jan 15, 2010 at 9:59 AM, Vitaly Babiy wrote:
> I have also been thinking about this, I think there is one problem but I am
> not sure. This is when you have functional test and they need talk to a
> database. In most cases you will be using transactions which should be fine,
> but if for s
On Thu, Jan 14, 2010 at 7:59 PM, Vitaly Babiy wrote:
> I have also been thinking about this, I think there is one problem but I am
> not sure. This is when you have functional test and they need talk to a
> database. In most cases you will be using transactions which should be fine,
> but if for s
I have also been thinking about this, I think there is one problem but I am
not sure. This is when you have functional test and they need talk to a
database. In most cases you will be using transactions which should be fine,
but if for some reason you can't use transaction for test this will have t
This is probably just a curiosity, but I was playing with ways to test
the raw power of my new 8-core mac pro and was looking at how to apply
this to testing.
By using multiprocessing I was able to reduce the running of the
current trunk tests from 6 minutes to 3.
Because a test case needs to be