Hi all,
As luis pointed out, one of my main concern was the time taken to run the
complete test suite before commiting. It painfully slow for the time being,
and people that are developping in ITK need to do it almost several times a
day. I can not make so many coffee breaks :-D
My basic assumpti
Hi Gaetan,
I agree that it is an interesting feature to be able to run several tests
simultaneously.
It is true that *the large majority* of ITK tests do not depend on the
output from
previous tests. There are however some exceptions, for example, the hole
filling
filters apply their computation
Selon Mathieu Malaterre <[EMAIL PROTECTED]>:
> Hi Alex "hanfei",
>
> I believe there is nothing in the ADD_TEST to declare dependencies.
> So chance is that you would run a test (depending on output from
> another) *before* the dependant test is run.
>
> Is this correct ?
But that's also the
That's correct...
Also, tests that pop up GUI windows and then do "screen analysis" to verify
that the test passes will quite often not work well in conjunction with each
other if two of them are run simultaneously...
On 7/25/07, Mathieu Malaterre <[EMAIL PROTECTED]> wrote:
Hi Alex "hanfei",
Hi Alex "hanfei",
I believe there is nothing in the ADD_TEST to declare dependencies.
So chance is that you would run a test (depending on output from
another) *before* the dependant test is run.
Is this correct ?
-Mathieu
On 7/24/07, Dr. Alex. GOUAILLARD <[EMAIL PROTECTED]> wrote:
hi all,
