office-gobmx/sw/qa
Xisco Fauli 7b0b6e5232 UITest_writer_tests7: improve test a bit
To see where the problem might be

Change-Id: I0baed63408c96eddffbaa39e172bc922c0a78241
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/146180
Tested-by: Jenkins
Reviewed-by: Xisco Fauli <xiscofauli@libreoffice.org>
2023-01-26 19:17:54 +00:00
..
api
complex/indeterminateState
core include filename if the test fails 2023-01-26 11:00:56 +00:00
extras tdf#146248: sw: move UItest to CppUnittest 2023-01-26 15:39:45 +00:00
filter sw HTML import: initial CSS support on tables 2023-01-20 13:40:22 +00:00
inc
python
uibase sw: add a new .uno:DeleteSections UNO command 2023-01-20 12:41:19 +00:00
uitest UITest_writer_tests7: improve test a bit 2023-01-26 19:17:54 +00: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.