office-gobmx/sw/qa
Bakos Attila 54031e6a29 tdf#132483: DOCX import: fix OLE anchoring position
The relative orientation of OLE objects was
not copied from the replacement object to
OLE, resulting bad position.

Co-authored-by: Attila Bánhegyi (NISZ)

Change-Id: If62124e5a40218a224e047efbe86a09606b44af5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/98493
Tested-by: László Németh <nemeth@numbertext.org>
Reviewed-by: László Németh <nemeth@numbertext.org>
2020-07-13 15:47:15 +02:00
..
api
complex/indeterminateState
core
extras tdf#132483: DOCX import: fix OLE anchoring position 2020-07-13 15:47:15 +02:00
inc
python
uibase
uitest uitest : Fix the old demo of writer comments 2020-07-09 16:34:17 +02:00
unit
unoapi
README

You can find different types of Writer tests here, the following directories
are available:

- core:
  - filters-test: loads different file types (see SwFiltersTest::testCVEs() for
    the list of supported filter types), and only makes sure Writer does not
    crash. To add new tests, you just need to drop in the test files to the
    relevant directory, no code change is necessary.
  - uwriter: this test has access to private Writer symbols, add new tests here
    if you need that.
- extras:
  - see its own README -- executes import and export filters and asserts the
    UNO model to verify the resulting document is the expected one.
  - also, any new C++ test that links to libsw (but does not need access to
    private Writer symbols) should go in this directory, whether using the UNO
    API or the internal one.
- complex: JUnit-based tests using the UNO API
- unoapi: JUnit-based test trying to get/set every UNO property, etc.