Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index


Hi,

On Fri, 2013-03-22 at 10:58 +0100, Miklos Vajna wrote:
Hi David,

On Thu, Mar 21, 2013 at 10:42:27AM +0100, David Ostrovsky wrote:
I wonder if it would make sense to establish
Python_test machinery in our build system to be able to write such and
many other tests in python instead and just say make Pytest_sw_complex
instead of make JunitTest_sw_complex (python have got unittest module
that we can start with)?

Hmm, yes, I think that would be an improvement.
done :-)
make PythonTest_sw_python

Python test machinery (in process) is up and running on system and
internal python and on all platforms. Many thanks to Michael S. and
Stephan for helping out with this!

so I migrated the fdo#55814 java unit test to python:
sw/qa/complex/writer/VarFields.java
sw/qa/python/var_fields.py

Problem (as i described in the python test file):
while java unit test is failing as expected, python unit test doesn't
fail...

Unlike in java, field's test condition is not get overridden in python.
Apparently xDoc.refresh() is somehow broken (from python), because doing
the update manually "fix" this:
1. run the python test: make PythonTest_sw_python
2. open created document
workdir/unxlngx6.pro/PythonTest/sw_python/VarFields.odt
3. check that TextSection's condition still has the right value: "foo EQ
1"
4. update field with Tool=>Update=>Fields (or [F9])
5. check that TextSection's condition was overridden: "0"

Another UNO bug?

Thanks
David


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.