office-gobmx/sw/qa
Mike Kaganski da77aec27e Fix flaky test on Win64
Obviously the left values are unstable; they were excluded on macOS,
and they fail exactly on the same lines for me locally on Win64 build.
So just test that the values are restored after delete and undo.

Change-Id: I63dc50d223edb052a0ada200189cef94c2e0f8e5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/130738
Tested-by: Mike Kaganski <mike.kaganski@collabora.com>
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
2022-03-01 10:47:07 +01:00
..
api
complex/indeterminateState
core
extras Fix flaky test on Win64 2022-03-01 10:47:07 +01:00
inc
python
uibase
uitest uitest: simplify tests even more 2022-02-28 22:28:05 +01: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.