Testing/Working on PyUNO?

[Stephan Bergmann]

On 02/19/2014 12:02 PM, Stephan Bergmann wrote:
> So, what can we do here?  How about an additional code module dedicated
> to subsequentchecks written in Python, which, while serving the useful
> purpose of testing specific application functionality (and in which role
> they may deliberately duplicate existing "native" tests), are meant more
> as a means to improve the PyUNO situation.
>
> 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.

Let me know whether that is useful.

Happy hacking,
Stephan