office-gobmx/sw/qa
Ilmari Lauhakangas 72186f02c1 tdf#127652: move UItest to CppunitTest
Change-Id: Id04414d00f92a0c32c38a9dd706d6656ba280746
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/98597
Tested-by: Jenkins
Tested-by: Xisco Fauli <xiscofauli@libreoffice.org>
Reviewed-by: Xisco Fauli <xiscofauli@libreoffice.org>
2020-07-16 13:59:16 +02:00
..
api
complex/indeterminateState
core tdf#134431 sw: fix crash on setting anchor of textbox while splitting a para 2020-07-14 09:02:27 +02:00
extras tdf#127652: move UItest to CppunitTest 2020-07-16 13:59:16 +02:00
inc
python Don't rely on Python's treatment of unrecognized escape sequences 2020-07-13 22:23:44 +02:00
uibase
uitest tdf#127652: move UItest to CppunitTest 2020-07-16 13:59:16 +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.