On Oct 3, 2007, at 11:08 , Damien Cassou wrote:

> 2007/10/3, Romain Robbes <romain.robbes at gmail.com>:
>> Well, writing a unit test for this will be a pain. It's a one- 
>> method change,
>> should I really write a new test class compiling several methods,  
>> somehow
>> bypassing user input to return an accurate answer, decompiling and  
>> comparing
>> the source code with an expected result, and remove the temporary  
>> methods
>> just for this?
>
> I'm just telling you what the release team is waiting for. But your
> arguments are right :-).

I thought the requirement was to not break any unit tests. Requiring  
every enhancement to come with a unit test is silly.


- Bert -