Great work!
Now the test cases in Tempest are well-stocked so it's a good time to
rearrange the design of test codes.
I checked mailing lists, IRC log and etherpads relating to this topic.
Let me leave my 5 thoughts below.
How to handle:
1. Data type (e.g, int, bool)
2. Specific value or
in Tempest
-Original Message-
From: David Kranz [mailto:dkr...@redhat.com]
Sent: Wednesday, November 13, 2013 4:33 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [qa] moratorium on new negative tests in Tempest
So that is the starting point. Comments
On 11/12/2013 02:33 PM, David Kranz wrote:
On 11/12/2013 01:36 PM, Clint Byrum wrote:
Excerpts from Sean Dague's message of 2013-11-12 10:01:06 -0800:
During the freeze phase of Havana we got a ton of new contributors
coming on board to Tempest, which was super cool. However it meant we
had
-
From: pcrews [mailto:glee...@gmail.com]
Sent: Tuesday, November 12, 2013 2:03 PM
To: Monty Taylor; openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [qa] moratorium on new negative tests in Tempest
On 11/12/2013 12:20 PM, Monty Taylor wrote:
On 11/12/2013 02:33 PM, David Kranz wrote
