observed the following failure in today's master build:
======================================================================
FAIL: test_tracked_changes_reject (trackedChanges.trackedchanges)
----------------------------------------------------------------------
Traceback (most recent call last):
File "master/sw/qa/uitest/writer_tests/trackedChanges.py", line 98,
in test_tracked_changes_reject
self.assertEqual(document.Text.String[0:1], "")
AssertionError: 'T' != ''
- T
+
my pet theory based entirely on speculation is that in the test code:
self.xUITest.executeCommand(".uno:TrackChanges")
type_text(xWriterEdit, "Test LibreOffice")
self.xUITest.executeCommand(".uno:ShowTrackedChanges")
the ".uno:TrackChanges" is somehow async dispatched and there is a loop
(in WindowUIObject::execute) to convert the "TYPE" action into a
KeyEvent per character and somehow after handling of the first "T" the
async event of the ".uno:TrackChanges" is executed.
does the UITest use processEventsToIdle at some point to avoid reorderings?
Context
- UITest/writer_tests: FAIL: test_tracked_changes_reject (trackedChanges.trackedchanges) · Michael Stahl
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.