History

Mike Kaganski 275aebc508 tdf#163064: pic element is required here, after all In commit `cf15306ccf` (ERROR: Invalid content was found starting with element 'p:pic'., 2014-12-22), the pic element inside the oleObj element was only alloswed for the old revision of ECMA-736 export, because that was considered invalid by officeotron. However, as of ECMA-376-1:2016, this element is mandatory; CT_OleObject definition in Annex A has: <xsd:element name="pic" type="CT_Picture" minOccurs="1" maxOccurs="1"/> and Annex L (Primer) has L.7.2.5 "Embeddings in a PresentationML Document" saying: The oleObj element shall have a pic child element that (optionally) contains the image data to be used in place of loading the actual object data. The omission of this in the export is the reason of tdf#163064. So here I filter out the error from the validation results, which is not ideal (I have no way to know if the found pic is really in the oleObj, or somewhere else), but a lesser evil, compared to required exclusion of all tests that export OLE objects. Change-Id: Ia73a49da7347e8ff22c626e211b55ba1e0625070 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/173761 Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com> Tested-by: Jenkins		2024-09-21 22:33:12 +02:00
..
qa/cppunit	loplugin:ostr in test	2024-05-14 11:47:53 +02:00
signing-keys
source	tdf#163064: pic element is required here, after all	2024-09-21 22:33:12 +02:00
user-template
CppunitTest_test_a11y.mk	CppunitTest_test_a11y: Missing test dependency	2024-02-26 16:00:38 +01:00
CppunitTest_test_xpath.mk
IwyuFilter_test.yaml
Library_subsequenttest.mk	tdf#45904: Move _Footnote Java tests to C++	2023-08-27 10:51:38 +02:00
Library_test.mk	this duplicated CPPUNIT_ASSERT_POINT_EQUAL_WITH_TOLERANCE	2024-01-20 17:10:56 +01:00
Library_test_setupvcl.mk
Library_vclbootstrapprotector.mk
Makefile
Module_test.mk
Package_unittest.mk
README.md
README.vars

README.md

Test Harness Code for C++ Unit Testing

Many of these tests are run during the build process. In that case on unix, if a test fails follow the error messages to debug it under gdb.