office-gobmx/sw/qa
Attila Bakos 2150fdc7d0 tdf#131539 DOCX export: fix position of OLE objects
Keeping position of OLE objects anchored to text
as a character.

Co-developer: Tibor Nagy (NISZ)
Change-Id: I9699250ae5c418f9994ea2a7a3b102681b042214
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/91983
Tested-by: László Németh <nemeth@numbertext.org>
Reviewed-by: László Németh <nemeth@numbertext.org>
2020-04-28 10:18:08 +02:00
..
api
complex/indeterminateState
core tdf#131729 sw: handle no drawing objects when calculating overlap of objects 2020-04-28 09:03:18 +02:00
extras tdf#131539 DOCX export: fix position of OLE objects 2020-04-28 10:18:08 +02:00
inc
python
uibase sw: prefer ODF over RTF when pasting from Writer 2020-04-22 20:08:20 +02:00
uitest tdf#131936 Correctly detect OOXML variant on import 2020-04-23 12:00:28 +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.