Age | Commit message (Collapse) | Author |
|
Change-Id: If52fb46f61962827acc08025617d9d61a6ab6d40
|
|
Change-Id: I0399a9557170de7d45f0fffbcb2c00a8f084010b
|
|
Change-Id: Ibd12835cc5368080a302b3b8d7c6f52ccc434e3c
|
|
Change-Id: Id1e3a761765c1e860f611f40a78a6c24fa17d055
|
|
Change-Id: I705e05878015f5c8aad993219ea89ea9d47f07fb
|
|
Change-Id: I4800ad80f1b447cae03664653285f1917ad3ee7e
|
|
Change-Id: Id271f10ac82ebae9fedd68d30c7f44435d60751d
|
|
Change-Id: I6ce22ecd6295bd8ad302d0f53c783f4ac2a1a036
|
|
Change-Id: I408c9aa0b80971f326b607b274ce046c27098f74
|
|
Change-Id: I256a029afefe5990dfb0c87859bae4508f5920bc
|
|
Change-Id: I6ef275c6a978db0da59da953511105c407a66f72
|
|
<sigh> pagebreak implementation is still flawed here, the used
range is used to determine whether the page break should be
considered ( or not ) Problem is that it is not the used
range but rather the rightmost column position that contains content
( but not necessarily the column that contains content but rather
the righmost column that has content ( or even that is covered either
by spillover from an adjacent column or drawing )
Change-Id: I68c8ccc5911049bc4b2076992f839bc684d966a9
|
|
Change-Id: I6d33ce8fe2333e7920b5c6cf82531ee859352748
|
|
Change-Id: I6289aa7e7872cc0c6aacd89f0679609792d37c28
|
|
also tests ListBox.AddItem & ListBox.Clear ( plenty of room
to flesh these tests out )
Change-Id: Iddaa5a5e6b406359c6215ad726085d3696e633cf
|
|
Change-Id: I8a6e2aeb3766a3890c5026129794b25cfa5c7ba5
|
|
Change-Id: If8ce9e5ce35c438b31234aab410b37f12eb1b1f4
|
|
Change-Id: I7b06c463a11b5d6442f69130e9eee767004e426f
|
|
Change-Id: I550141e0ada38d80bfac0a0a296bf3dd9116af71
|
|
Note: some of the test documents have some tests disabled in order to run
without errors, these are identified by the following lines
Rem [#FIXME disabled 3.6 ] in the macro source.
note: some of these errors are expected and were always happening, some
errors e.g. those pastespecial specific ones in
qa/unit/data/xls/TestCalc_Rangetest2.xls
seem to be to do with problems with the test harness.
note: there are some others ( e.g. in Window.xls & windows2.xls ) that seem
to be related to hard sizes and screen resolution ( these should be adjusted
sensibly )
Change-Id: I07a43a2802d4e1794ac2f8c648f666b5bcd13a04
|
|
In calc, we see a lot of implementations of createFileURL. So get ride
of all it and start to use the UnoAPitest::createFileURL method.
Also, clean the UnoApiRest::createFileURL method, fix the path from UnoApiTest and
moved some testing files to the right dir that the file belongs.
Conflicts:
sc/qa/extras/scoutlineobj.cxx
Change-Id: Ic02f13777503729ac70da590f4a42866f17ea9b2
|
|
Change-Id: Iea0576e61963dbdb72c88fe332c7cfe3e8ab7ff0
Reviewed-on: https://gerrit.libreoffice.org/1794
Reviewed-by: Noel Power <noel.power@suse.com>
Tested-by: Noel Power <noel.power@suse.com>
|
|
Change-Id: I1fa77c874c6307ff71ea0aeee653acf1305f2646
Reviewed-on: https://gerrit.libreoffice.org/1736
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
Tested-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
|
|
Change-Id: I689be9776c4d1fe7d931446d62ea8b1fd733de92
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
add a typo correction on xnamedranges.cxx
|
|
renaming previous test to XRangeNames
new test for XRangeName
|
|
one test disabled because we first need to write a patch for our
internal cppunit
|
|
it seems that the java based test fails by "design" and not due to an
error
|
|
|