Also curious about this. It seems weird to separate the 'positive' and
the 'negative' ones, assuming those patches are mostly contributed by
the same group of developers.
Yeah, agree. This approach leads to situation when I need to look at two
places to observe test coverage for each component.
On Thu, Mar 17, 2016 at 3:24 PM, Kairat Kushaev wrote:
>
> Also curious about this. It seems weird to separate the 'positive' and
> the 'negative' ones, assuming those patches are mostly contributed by
> the same group of developers.
>
>
> Yeah, agree. This approach leads
On Wed, Mar 16, 2016 at 10:41 PM, Jim Rollenhagen
wrote:
> On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote:
>> Hi
>>
>> I have one proposal[1] related to negative tests in Tempest, and
>> hoping opinions before doing that.
>>
>> Now Tempest contains
2016-03-16 20:27 GMT-07:00 Assaf Muller :
> On Wed, Mar 16, 2016 at 10:41 PM, Jim Rollenhagen
> wrote:
>> On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote:
>>> Hi
>>>
>>> I have one proposal[1] related to negative tests in Tempest, and
On Thu, Mar 17, 2016 at 2:57 AM Ken'ichi Ohmichi
wrote:
> 2016-03-16 19:41 GMT-07:00 Jim Rollenhagen :
> > On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote:
> >> Hi
> >>
> >> I have one proposal[1] related to negative tests in
Totally agree here, also, having positive/negative API tests in Tempest
helps in the API stability effort. Although the API is owned by the service
in question, it interacts with other services and making sure the API is
stable is valuable for the communication between them.
We know a recent
Hi,
On Thu, Mar 17, 2016 at 2:20 AM, Ken'ichi Ohmichi
wrote:
> Hi
>
> I have one proposal[1] related to negative tests in Tempest, and
> hoping opinions before doing that.
>
> Now Tempest contains negative tests and sometimes patches are being
> posted for adding more
2016-03-17 5:32 GMT-07:00 Adam Young :
> On 03/16/2016 11:01 PM, Ken'ichi Ohmichi wrote:
>>
>> 2016-03-16 19:29 GMT-07:00 Adam Young :
>>>
>>> On 03/16/2016 09:20 PM, Ken'ichi Ohmichi wrote:
Hi
I have one proposal[1] related to negative
On Fri, Mar 18, 2016 at 9:06 AM, Ken'ichi Ohmichi wrote:
> 2016-03-17 4:05 GMT-07:00 Andrea Frittoli :
>> On Thu, Mar 17, 2016 at 2:57 AM Ken'ichi Ohmichi
>> wrote:
>>>
>>> 2016-03-16 19:41 GMT-07:00 Jim Rollenhagen
El 17/03/16 a las 04:27, Assaf Muller escribió:
> On Wed, Mar 16, 2016 at 10:41 PM, Jim Rollenhagen
> wrote:
>> On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote:
>>> Hi
>>>
>>> I have one proposal[1] related to negative tests in Tempest, and
>>> hoping
2016-03-17 3:22 GMT-07:00 Jordan Pittier :
>>
>> If wanting to add negative tests, it is a nice option to implement
>> these tests on each component repo with Tempest plugin interface. We
>> can avoid operating negative tests on different component gates and
>> each
2016-03-17 15:05 GMT-07:00 Rochelle Grober :
> (Sorry for the top post. It was this or bottom post because of company
> choice of email systems)
(no problem :)
> Integration tests, corner cases, negative tests. Lots of names that don't
> have clear definitions in
On 03/16/2016 11:01 PM, Ken'ichi Ohmichi wrote:
2016-03-16 19:29 GMT-07:00 Adam Young :
On 03/16/2016 09:20 PM, Ken'ichi Ohmichi wrote:
Hi
I have one proposal[1] related to negative tests in Tempest, and
hoping opinions before doing that.
Now Tempest contains negative
From: GHANSHYAM MANN <ghanshyamm...@gmail.com>
Subject: Re: [openstack-dev] [QA][all] Propose to remove negative tests from
Tempest
Date: Fri, 18 Mar 2016 10:05:39 +0900
> On Fri, Mar 18, 2016 at 9:06 AM, Ken'ichi Ohmichi <ken1ohmi...@gmail.com>
> wrote:
>> 2016-03-
On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote:
> Hi
>
> I have one proposal[1] related to negative tests in Tempest, and
> hoping opinions before doing that.
>
> Now Tempest contains negative tests and sometimes patches are being
> posted for adding more negative tests, but
2016-03-17 4:05 GMT-07:00 Andrea Frittoli :
> On Thu, Mar 17, 2016 at 2:57 AM Ken'ichi Ohmichi
> wrote:
>>
>> 2016-03-16 19:41 GMT-07:00 Jim Rollenhagen :
>> > On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi
(Sorry for the top post. It was this or bottom post because of company choice
of email systems)
Integration tests, corner cases, negative tests. Lots of names that don't have
clear definitions in this discussion. But, it seems like the collection of
"negative tests" include both functional
2016-03-18 1:50 GMT-07:00 Masayuki Igawa <masayuki.ig...@gmail.com>:
> From: GHANSHYAM MANN <ghanshyamm...@gmail.com>
> Subject: Re: [openstack-dev] [QA][all] Propose to remove negative tests from
> Tempest
> Date: Fri, 18 Mar 2016 10:05:39 +0900
>
>> On Fri,
On 03/16/2016 09:20 PM, Ken'ichi Ohmichi wrote:
Hi
I have one proposal[1] related to negative tests in Tempest, and
hoping opinions before doing that.
Now Tempest contains negative tests and sometimes patches are being
posted for adding more negative tests, but I'd like to propose
removing
2016-03-16 19:29 GMT-07:00 Adam Young :
> On 03/16/2016 09:20 PM, Ken'ichi Ohmichi wrote:
>>
>> Hi
>>
>> I have one proposal[1] related to negative tests in Tempest, and
>> hoping opinions before doing that.
>>
>> Now Tempest contains negative tests and sometimes patches are
Most negative test supposed to be very simple and we should not spend
too much time in them.
The right question:
Are we able to run 100 negative test/sec ?
Where is the time spent ?
If we are able to solve the main issue,
probably we do not need to worry about how many negative test we have.
2016-03-16 19:41 GMT-07:00 Jim Rollenhagen :
> On Wed, Mar 16, 2016 at 06:20:11PM -0700, Ken'ichi Ohmichi wrote:
>> Hi
>>
>> I have one proposal[1] related to negative tests in Tempest, and
>> hoping opinions before doing that.
>>
>> Now Tempest contains negative tests and
On Wed, Mar 16, 2016 at 10:29:48PM -0400, Adam Young wrote:
> On 03/16/2016 09:20 PM, Ken'ichi Ohmichi wrote:
> >Hi
> >
> >I have one proposal[1] related to negative tests in Tempest, and
> >hoping opinions before doing that.
> >
> >Now Tempest contains negative tests and sometimes patches are
>
> I'd love to see this idea explored further. What happens if Tempest
> ends up without tests, as a library for shared code as well as a
> centralized place to run tests from via plugins?
>
Also curious about this. It seems weird to separate the 'positive' and
the 'negative' ones, assuming
I do think negative tests should live on, most likely in their own
tempest-plugin based repository. However, I'm not sure that I agree with the
reason being because they are functional tests rather than integration. If you
look at the current tests, one could argue that many non-Nova tests are
Main reason to split negative tests out, that I see, is attempt to remove
"corner, not integrational" tests out of Tempest tree. If so, then
"negative" tests is not proper choice, I think.
Tempest has lots of positive "corner" test cases. So, if move something,
then we need to move exactly
26 matches
Mail list logo