[katello-devel] katello-dev-box proposal

Dmitri Dolguikh dmitri at redhat.com
Thu Aug 16 09:35:10 UTC 2012


On 16/08/12 09:58 AM, Ivan Nečas wrote:
> On 08/16/2012 10:44 AM, Dmitri Dolguikh wrote:
>> On 16/08/12 09:38 AM, Ivan Nečas wrote:
>>>
>>>
>> No, it means you have problems with your tests and/or code coverage.
>> -d
> How unit tests solve this scenario:
>
> 1. you have separate unit tests for CLI and API, all green
> 2. you decide to improve the API, make unit tests green again (forget 
> about CLI, because green tests is what you care about)
>
> result: green tests and broken code, green tests =! working code.
>
> And I don't think "my tests are green" is valid reason to close any 
> bugzilla.
>
> So you have 2 options: spent the rest of your life writing unit tests 
> to simulate all the possible scenarios. Or you run all the code (with 
> all the other moving parts) and test against it.
>
I never said anything about detecting changes in sub-components of the 
system. That is not the purpose of unit- (developer-) tests. You need a 
set of tests periodically exercising integration points that a given 
component relies on. Unit tests cover the rest.
-d




More information about the katello-devel mailing list