Open Stack

On 05/07/2013 03:44 PM, Kashyap Chamarthy wrote:
> On 05/08/2013 01:03 AM, Sean Dague wrote:
>> As a follow up to our session on Tempest Best Practices at the summit, I'm beginning down
>> the path of the restructure of the Tempest repository, trying to go with a "get a README
>> approved first, then do" approach.
>>
>> So here is the first review - https://review.openstack.org/#/c/28453/
>>
>> Please provide your feedback, either in the review, or here on list. And once that is
>> approved and in, I'll go forward with doing some incremental changes. My theory on order is:
>>
>> cli
>> scenario
>> stress
>> 3rdparty
>
> Can you please elaborate what did you have in mind here? 3rd party 'companies' ?

Sure, please look at the review, it should enlighten things. Basically a 
place for tests which test 3rdparty APIs that OpenStack implements in 
core. They by definition aren't the OpenStack API, but have a place in 
our test suites.

At one level I think about each directory as a chance to write a 
different set of hacking rules that will automatically enforce which 
libraries can be used to ensure they stay pure.

>> api
>
> performance (?)
> 	- Doesn't have to be full featured. Some minimal set which might give a rough view
> whether its improving/degrading.
>
> I wonder what others here think. Whether its too much or out of scope (due to time
> constraints or other factors I haven't taken into account here).

	-Sean

-- 
Sean Dague
http://dague.net