Open Stack

On 13-06-18 11:14 AM, Anita Kuno wrote:
> On 13-06-18 09:34 AM, Anita Kuno wrote:
>> On 13-06-18 04:59 AM, Thierry Carrez wrote:
>>> Personally I would introduce a TESTING file that would describe all 
>>> available methods for running tests,
Actually I should point out that in my approach, I went with the minimum 
instructions to get a newcomer up and running tests across (hopefully) 
all projects with links that can describe all available methods for 
running tests, including this link: https://wiki.openstack.org/wiki/Testing

My motivation is to lower the barrier to entry for new contributors and 
encourage them to source more efficient testing methods on their project 
of choice AFTER they have experienced some form of success testing 
OpenStack code.

Commentary on the validity of my direction welcome.

Thanks,
Anita.
>>> and rename/move run_tests.sh to something less discoverable... so 
>>> that people looking for ways to run tests would find TESTING first. 
>>> Then if developers care about any alternate method they will 
>>> maintain it, and if it's unmaintained it can be removed. 
>> Oh, I do like this suggestion. I know it was also suggested last 
>> night in the -infra channel so thanks to who suggested it there as well.
>>
>> Since I am already creating something similar for internal purposes, 
>> I can take a run at this. Perhaps I should start with one for olso?
> Here is my initial patch in oslo for a TESTING file: 
> https://review.openstack.org/#/c/33456
>
> I welcome your help to improve this patch so that it can become accepted.
>>
>> Thanks,
>> Anita.
>>
>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>