Weeeellllllll,

part of the goal of the upcoming refactor is to tear down that massive
libdev suite runner, and provide smaller, more digestible, better tested,
and much better documented packages. In the meantime, I think that the
update to the wiki should suffice?

On Mon, Jul 27, 2009 at 10:46 PM, Paul Oppenheim (Poppy Linden) <
po...@lindenlab.com> wrote:

> Oh! i *just* got similar info from kartic:
>
> bin/python `which nosetests` src/*
>
> it's /really/ not obvious that you need nose to run the unit tests outside
> the massive libdev suite runner. Where would that nugget of knowledge best
> go?
>
> + poppy
>
> Enus Linden wrote:
>
>> Last week I removed the zope.testrunner wrappers, and updated the docs to
>> reflect the usage of nose to run unit tests.
>>
>> http://wiki.secondlife.com/wiki/Pyogp/Client_Lib#Pyogp_Unit_Tests
>>
>> nosetests --where=src/pyogp.lib.base/
>> ----------------------------------------------------------------------
>> Ran 139 tests in 21.987s
>>
>> There is an implied requirement that pyogp's dependencies be in the
>> PYTHONPATH.
>>
>> I'll be working on extending docs and test coverage as we do our packaging
>> work.
>>
>> ~e
>>
>> On Mon, Jul 27, 2009 at 9:20 PM, Paul Oppenheim (Poppy Linden) <
>> po...@lindenlab.com <mailto:po...@lindenlab.com>> wrote:
>>
>>    It doesn't seem there's an easy way to run all the tests in just
>>    pyogp.lib.base. Am I missing some gem of python introspection, or is
>>    it genuinely not possible?
>>
>>    + poppy
>>    _______________________________________________
>>    Click here to unsubscribe or manage your list subscription:
>>    https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp
>>
>>
>>
>
_______________________________________________
Click here to unsubscribe or manage your list subscription:
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp

Reply via email to