office-gobmx/sw/qa
Miklos Vajna d1278ef484 bnc#865381 DOCX import: handle <w:hideMark> table cell property
Change-Id: Id0dd34110376168e34df4956869608895b86abfe
2014-08-14 15:55:44 +02:00
..
complex java: remove commented out code 2014-08-14 10:59:48 +02:00
core warning C4245: 'initializing' : conversion from 'int' to 'sal_uLong'... 2014-08-13 10:10:51 +02:00
cppunit/tox
extras bnc#865381 DOCX import: handle <w:hideMark> table cell property 2014-08-14 15:55:44 +02:00
python sw: use less confusing variable names in python test 2014-08-14 14:39:02 +02:00
tiledrendering
unoapi
README

You can find different types of Writer tests here, the most interesting ones:

- 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.
- core/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.