[...]
[1] So that the usefulness of getting results of all tests with the
same
basename is retained when refactoring.
Bad premise; the tests don't have to be renamed.
So it does not matter if the default is true or false.
I didn't get what the trade-off is. If there is none, then ever
On 18 July 2013 22:15, Gilles wrote:
> On Thu, 18 Jul 2013 20:35:53 +0100, sebb wrote:
>>
>> On 18 July 2013 20:06, Gilles wrote:
>>>
>>> On Thu, 18 Jul 2013 16:19:10 +0100, sebb wrote:
Some MATH unit tests take a long time to run.
One example is CMAESOptimizerTest, which
On 7/18/13 2:15 PM, Gilles wrote:
> On Thu, 18 Jul 2013 20:35:53 +0100, sebb wrote:
>> On 18 July 2013 20:06, Gilles wrote:
>>> On Thu, 18 Jul 2013 16:19:10 +0100, sebb wrote:
Some MATH unit tests take a long time to run.
One example is CMAESOptimizerTest, which is run twice -
On Thu, 18 Jul 2013 20:35:53 +0100, sebb wrote:
On 18 July 2013 20:06, Gilles wrote:
On Thu, 18 Jul 2013 16:19:10 +0100, sebb wrote:
Some MATH unit tests take a long time to run.
One example is CMAESOptimizerTest, which is run twice - once for
the
deprecated code and once for the new code.
On 18 July 2013 20:06, Gilles wrote:
> On Thu, 18 Jul 2013 16:19:10 +0100, sebb wrote:
>>
>> Some MATH unit tests take a long time to run.
>>
>> One example is CMAESOptimizerTest, which is run twice - once for the
>> deprecated code and once for the new code.
>>
>> Would it make sense to exclude t
On Thu, 18 Jul 2013 16:19:10 +0100, sebb wrote:
Some MATH unit tests take a long time to run.
One example is CMAESOptimizerTest, which is run twice - once for the
deprecated code and once for the new code.
Would it make sense to exclude the long-running tests of deprecated
classes by default?
Some MATH unit tests take a long time to run.
One example is CMAESOptimizerTest, which is run twice - once for the
deprecated code and once for the new code.
Would it make sense to exclude the long-running tests of deprecated
classes by default?
Or maybe all the tests of deprecated classes shoul
