Open Stack

John, Monty, Mark,

I think one example is unit tests involving test case against entry
points which requires installation.  I guess that's John's most
annoying thing.

For this special case, I think switching from run_tests.sh to tox (or
even ditching run_tests.sh) is the right solution.  I'm working on a
patch for Cinder to make this change
(https://review.openstack.org/#/c/21597/).   It's not ready yet as I
met some difficulty with coverage tests, but as a starter, you can try
functionality other than coverage tests.

On Sun, Feb 10, 2013 at 5:23 AM, Monty Taylor <mordred at inaugust.com> wrote:
>
>
> On 02/09/2013 01:59 PM, Mark McLoughlin wrote:
>> Hi John,
>>
>> On Sat, 2013-02-09 at 12:15 -0700, John Griffith wrote:
>>> We seem to be going down a path of requiring more and more infrastructure
>>> and reliance from modules inside of the respective projects code base, and
>>> lately (the most annoying thing to me) is actually requiring the
>>> installation of the project and it's services in order for our unit tests
>>> to run.
>>
>> Got an example?
>
> Yes. I'd also like an example.
>
> FWIW - I agree with the sentiment that our unittests should be simple to
> run and that cross-project testing should be the purview of integration
> tests.
>
> Monty
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Regards
Huang Zhiteng