Testing/Working on PyUNO?

[Kevin Hunter Kesling]

At 6:09am -0500 Thu, 20 Feb 2014, Stephan Bergmann wrote:
> On 02/19/2014 12:02 PM, Stephan Bergmann wrote:
>> The idea would be that Kevin (and others) would fill this with PyUNO
>> coding scenarios that cross their mind, discover errors in the PyUNO
>> infrastructure, ideally distill tests for those specific errors out of
>> the more general tests (that could then even go into more specific code
>> modules like pyuno or testtools), and eventually prune test snippets
>> again that are no longer useful.
>
> To get that started, I created
> <http://cgit.freedesktop.org/libreoffice/core/commit/?id=4e887567c5b4b06646ab1340376e240d6c5af9cb>
> "A rudimentary framework for additional Python tests not run by default"
> and moved the previously abandoned
> <http://cgit.freedesktop.org/libreoffice/core/commit/?id=f2471280c7c625e39369f76bd0efa1d2402f62bf>
> "Test for fdo#74824" there.
>
> At least for now, the tests are not run by default, but need an explicit
> "make PythonTest_pytests".  See the commit message of
> <http://cgit.freedesktop.org/libreoffice/core/commit/?id=4e887567c5b4b06646ab1340376e240d6c5af9cb>
> for details.

That's great, and now means that there is at least an appropriate place 
to put the functional tests that are currently in my purview.  If James 
DuPont (for instance, since he commented on this thread, and [hint, 
hint]) were able to identify problem areas he's run across in test form, 
that would be most appreciated as well!  :-)

Cheers,

Kevin