[katello-devel] CLI tests with better granularity

Dmitri Dolguikh dmitri at redhat.com
Mon Jul 25 12:12:26 UTC 2011


On 11-07-25 8:39 AM, Lukas Zapletal wrote:
> On 07/22/2011 02:48 PM, Dmitri Dolguikh wrote:
>> Perhaps we should look into writing real developer tests? The ones we
>> currently have because of their nature are only going to get slower; we
>> can configure jenkins to run them a couple of times a day.
>
> What on Earth are "developer tests"?
Any test that was intended to be run by a developer, as part of 
development process.
>
> I am familiar with unit tests, integration tests and system tests, but 
> never heard about developer tests.
>
> The problem of integration/system tests is need of full setup. 
> Prerequisite for running them is installation tests.
>
> I think our target should be
>
> nightly build -> installation test -> integration test -> ui test
>
> I think we cannot live without them after we release first version of 
> the SE product.
I'm not suggesting getting rid of cli tests, but rather implementing 
them as a set of (mostly) unit tests, plus a set of katello api tests 
(which can be run once-twice a day). Current cli tests are quite slow 
and fragile, and they will only get more slow and fragile with time.

-d




More information about the katello-devel mailing list