Re: New "tests" namespace to share test code

Hi! We've had some more discussions regarding this topic within the CI team. Here's a brief summary of the recommendation we agreed upon: Tests may be written in different ways, but are enabled in a standard way directly in the package git repository as defined by the Standard Test Interface.

Re: New "tests" namespace to share test code

On 02/25/2018 08:59 PM, Pierre-Yves Chibon wrote: On Sun, Feb 25, 2018 at 12:12:33PM +, Zbigniew Jędrzejewski-Szmek wrote: On Thu, Feb 22, 2018 at 03:50:38PM +0100, Pierre-Yves Chibon wrote: On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote: Hi! During the last days there

Re: New "tests" namespace to share test code

On 03/01/2018 04:00 PM, Petr Šplíchal wrote: To sum up what I've heard so far from the developer side: * I would like to enable tests for my component (yes, I want) * I will take care of them (really, I see the benefit in CI) * I want to easily collaborate on tests with qe (direct commits) * I

Re: New "tests" namespace to share test code

>> To sum up what I've heard so far from the developer side: >> >> * I would like to enable tests for my component (yes, I want) >> * I will take care of them (really, I see the benefit in CI) >> * I want to easily collaborate on tests with qe (direct commits) >> * I don't want to give qe commit

Re: New "tests" namespace to share test code

On Thu, Mar 01, 2018 at 02:44:37PM +0100, Petr Šplíchal wrote: > > > > My worries are basically that this mechanism is hiding the > > > > tests from the package maintainers. It splits the concerns > > > > between people maintaining the artifacts and people > > > > maintaining the tests, which is

Re: New "tests" namespace to share test code

> > > My worries are basically that this mechanism is hiding the > > > tests from the package maintainers. It splits the concerns > > > between people maintaining the artifacts and people > > > maintaining the tests, which is exactly what the original > > > plan to bring CI was *not* about. > > >

Re: New "tests" namespace to share test code

On Sun, Feb 25, 2018 at 12:12:33PM +, Zbigniew Jędrzejewski-Szmek wrote: > On Thu, Feb 22, 2018 at 03:50:38PM +0100, Pierre-Yves Chibon wrote: > > On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote: > > > Hi! > > > > > > During the last days there have been concerns raised

Re: New "tests" namespace to share test code

On Thu, Feb 22, 2018 at 03:50:38PM +0100, Pierre-Yves Chibon wrote: > On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote: > > Hi! > > > > During the last days there have been concerns raised regarding > > what is an appropriate content for the tests namespace. [1] My > > original idea

Re: New "tests" namespace to share test code

On Fri, Feb 23, 2018 at 10:33:57AM +0100, Pavel Raiskup wrote: > On Thursday, February 22, 2018 3:50:38 PM CET Pierre-Yves Chibon wrote: > > On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote: > > > When, for a particular package, it is the most efficient way to > > > maintain tests in

Re: New "tests" namespace to share test code

On Fri, Feb 23, 2018 at 10:19:35AM +0100, Petr Šplíchal wrote: > On 22 February 2018 at 15:50, Pierre-Yves Chibon wrote: > > On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote: > >> Hi! > >> > >> During the last days there have been concerns raised regarding > >>

Re: New "tests" namespace to share test code

On Thursday, February 22, 2018 3:50:38 PM CET Pierre-Yves Chibon wrote: > On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote: > > When, for a particular package, it is the most efficient way to > > maintain tests in a separate repo why should we discourage from > > this approach? There

Re: New "tests" namespace to share test code

On 22 February 2018 at 15:50, Pierre-Yves Chibon wrote: > On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote: >> Hi! >> >> During the last days there have been concerns raised regarding >> what is an appropriate content for the tests namespace. [1] My >> original

Re: New "tests" namespace to share test code

On Wed, Feb 14, 2018 at 05:28:20PM +0100, Petr Šplíchal wrote: > Hi! > > During the last days there have been concerns raised regarding > what is an appropriate content for the tests namespace. [1] My > original idea was to enable sharing tests even across branches of > the same component, not

Re: New "tests" namespace to share test code

On Thu, 2018-02-15 at 13:11 +0100, Petr Šplíchal wrote: > > > The question 'who decides which tests block which packages' is > > left a bit up in the air, but in fact no more so than it already > > was for package-specific tests... > > Right. Do we want to change this? Specify this more

Re: New "tests" namespace to share test code

On 14 February 2018 at 18:18, Adam Williamson wrote: > On Wed, 2018-02-14 at 17:28 +0100, Petr Šplíchal wrote: >> Hi! >> >> During the last days there have been concerns raised regarding >> what is an appropriate content for the tests namespace. [1] My >> original idea

Re: New "tests" namespace to share test code

On Wed, 2018-02-14 at 17:28 +0100, Petr Šplíchal wrote: > Hi! > > During the last days there have been concerns raised regarding > what is an appropriate content for the tests namespace. [1] My > original idea was to enable sharing tests even across branches of > the same component, not only for

Re: New "tests" namespace to share test code

On 02/14/2018 05:28 PM, Petr Šplíchal wrote: Hi! During the last days there have been concerns raised regarding what is an appropriate content for the tests namespace. [1] My original idea was to enable sharing tests even across branches of the same component, not only for tests to be used by

Re: New "tests" namespace to share test code

Hi! During the last days there have been concerns raised regarding what is an appropriate content for the tests namespace. [1] My original idea was to enable sharing tests even across branches of the same component, not only for tests to be used by completely different packages. The initial

New "tests" namespace to share test code

Hi! While working on adding CI tests [0] using the Standard Test Interface a need arose to have a shared git repository where tests could be stored: * A large number of test files makes a dist-git repository more difficult to maintain * Tests might follow a different branching pattern than