office-gobmx/sw/qa
Andrea Gelmini 91809c9050 Removed executable bits on doc files
Change-Id: I20142959913d80e9fb683de8285e6ffde69741f8
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/137265
Tested-by: Jenkins
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
2022-07-21 16:15:05 +02:00
..
api
complex/indeterminateState [API CHANGE] Drop css::accessibility::XAccessibleStateSet 2022-07-08 10:10:11 +02:00
core Removed executable bits on doc files 2022-07-21 16:15:05 +02:00
extras use more concrete UNO classes in writer 2022-07-21 09:00:05 +02:00
filter/ww8
inc
python tdf#132293 remove unused imports and unused variables in sw 2022-06-30 09:57:38 +02:00
uibase
uitest tdf#148198: merge identical hyperlinks of adjacent text ranges on ODF export 2022-07-14 07:43:14 +02:00
unit Use a dedicated log area for a SAL_INFO in test code 2022-07-07 13:39:47 +02:00
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.