Integration per-component tests in Fedora

Honza Horak hhorak at
Tue Oct 21 11:53:43 UTC 2014

On 10/21/2014 01:17 AM, Matthew Miller wrote:
> On Mon, Oct 20, 2014 at 11:16:08PM +0200, Honza Horak wrote:
>> 1a) Include the tests in git for component, say in 'tests/'
>> directory. With this approach it would not be easy to use some
> [...]
>> 1b) Another approach would be to package the test suites as separate
>> components using standard packaging process called by some
>> convention and which would be installed as RPMs. With this approach
> [...]
> There was previously some discussion on this (I think on -devel? I'll
> look for the thread)

Ah, thanks, I probably found it:

> in context of tasktron. My suggestion of putting
> them in the RPMs was largely not supported by anyone else until you
> came along. :) I don't remember why not but I definitely remember
> backing off because everyone told me I was crazy. :)

So, the only disadvantage I found was that keeping tests further from 
components' sources might make users not keeping tests in sync with 

> One of the desirable things mentioned at that point was that it would
> be nice to not require package maintainers and test-writers/maintainers
> to be the same for a given package, and possibly different permission
> sets (proven-testers not necessarily proven-packagers).
> At that point someone suggested leaving the dist-git alone and creating
> a parallel tests-git, with some fedpkg linkage.

Sounds interesting, too. I also had on my mind an idea to utilize copr 
and it's dist-git, which I was told is going to be ready at some point.


More information about the env-and-stacks mailing list