office-gobmx/sw/qa
Michael Stahl 1b4bf7effc sw: HTML import: apply hard formatting at insert position ...
... even if there is a character format hint there - in this case, a
RES_TXTATR_AUTOFMT attribute will not be converted to the SwTextNode's
item set.

Also add a test that uses the XDocumentInsertable interface to insert
the HTML, which is closer to the real use case.

(follow-up to commit f45d2fa85b)

Change-Id: Idbf7efceabca8d43d3e32d0b29fb37a9322c184c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/177740
Reviewed-by: Michael Stahl <michael.stahl@allotropia.de>
Tested-by: Jenkins
2024-12-03 19:25:02 +01:00
..
api
complex/indeterminateState
core tdf#164090: a11y sw: add new warning for non numbered empty paragraph 2024-12-03 17:21:46 +01:00
extras sw: HTML import: apply hard formatting at insert position ... 2024-12-03 19:25:02 +01:00
filter
inc don't bother passing const std::[u16]string_view by reference 2024-12-03 15:18:31 +01:00
python
uibase tdf#146553 Enable additonal functions in editable section while in r/o mode 2024-11-29 01:15:51 +01:00
uitest tdf#163325: uitest: load the saved document 2024-12-02 12:22:57 +01:00
unit don't bother passing const std::[u16]string_view by reference 2024-12-03 15:18:31 +01:00
unoapi
writerfilter
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.