Return-Path: X-Original-To: apmail-openoffice-dev-archive@www.apache.org Delivered-To: apmail-openoffice-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E0D2818E8C for ; Sun, 11 Oct 2015 17:56:01 +0000 (UTC) Received: (qmail 25870 invoked by uid 500); 11 Oct 2015 17:55:56 -0000 Delivered-To: apmail-openoffice-dev-archive@openoffice.apache.org Received: (qmail 25796 invoked by uid 500); 11 Oct 2015 17:55:56 -0000 Mailing-List: contact dev-help@openoffice.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openoffice.apache.org Delivered-To: mailing list dev@openoffice.apache.org Received: (qmail 25771 invoked by uid 99); 11 Oct 2015 17:55:56 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 11 Oct 2015 17:55:56 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id E6007C1F61 for ; Sun, 11 Oct 2015 17:55:55 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.174 X-Spam-Level: ** X-Spam-Status: No, score=2.174 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, NML_ADSP_CUSTOM_MED=1.2, SPF_SOFTFAIL=0.972, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id qGvoUJe02zmj for ; Sun, 11 Oct 2015 17:55:46 +0000 (UTC) Received: from nm4-vm3.access.bullet.mail.bf1.yahoo.com (nm4-vm3.access.bullet.mail.bf1.yahoo.com [216.109.114.114]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 740D22045A for ; Sun, 11 Oct 2015 17:55:46 +0000 (UTC) Received: from [66.196.81.163] by nm4.access.bullet.mail.bf1.yahoo.com with NNFMP; 11 Oct 2015 17:55:39 -0000 Received: from [98.138.104.98] by tm9.access.bullet.mail.bf1.yahoo.com with NNFMP; 11 Oct 2015 17:55:39 -0000 Received: from [127.0.0.1] by smtp118.sbc.mail.ne1.yahoo.com with NNFMP; 11 Oct 2015 17:55:39 -0000 X-Yahoo-Newman-Id: 451874.90236.bm@smtp118.sbc.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: zqUwbyYVM1k94RcLUB8CjrPUbsXCcnmgfdCuJmxZDQqngzm EcGwlUT1x9F1cRnE5FscA0dkkwv0kGDvZKmBRdpxo2tPrUGBDcCepjJDXxoO rXh5QYojtA7GVpFKWsjHHtARVUxfQrP7MRWv7NgrBaDVL2IhVgLEikFtV4q_ A7CMSvyHNU9CPU4bOW4vp3woFpO0sed4SxDQbNAkp87o84lH0uxTHnpw9JH1 31V5xOi.juVEb0EVLli7JJvGaAb4_TvduJZPP3uvCCRXKIEi8CywL5gd4mgS itHmGXsPtvlNO17mIERtSx2UPHuXdmU18w9.q9T_ZLwD9ofF2rJbPob.FPTr HGLvTN1HlASVICc3K4bm8aln.A.m1UJMQOST4BGXOYmzAoaSX7uPo4ByRlVb gdDFJf46pd24JXqhXDysg5zN1Iz4Jya6ykue5xKRTrvQ45Ebq4K_xwdHv5C1 UfXtRBObCYhmvH9yQ5kOUpvPAZpmVB9kditSWO0QYoFPMAzYj9a3jWKDRqMw qnoeScz3rtQ2xGwYzO08DinCrvT1t7mVwDQE- X-Yahoo-SMTP: dHt73eiswBAYjuZ6oL.TTjbe.KQkAIve Subject: Re: Google Test migration - the conclusion To: dev@openoffice.apache.org References: From: Kay Schenk X-Enigmail-Draft-Status: N1110 Message-ID: <561AA297.4000105@gmail.com> Date: Sun, 11 Oct 2015 10:55:35 -0700 User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit On 10/11/2015 01:45 AM, Damjan Jovanovic wrote: > Hi > > So I've migrated the vast majority of cppunit unit tests to Google > Test, and completely removed cppunit from our tree (no > --with-system-cppunit option to configure, no dmake makefile, no > gbuild script, nothing). There is a few last remaining tests using > cppunit or otherwise problematic, but they're extremely difficult to > fix: > > 1. main/configmgr/qa/unit > Moved to Google Test, but all tests fail on *nix, and it doesn't even > want to start running on Windows. It seems to have been broken long > ago, and someone more familiar with UNO should fix it. Doesn't run > during the build. > > 2. main/sal/qa/rtl_strings > Doesn't compile, curly braces don't match, and I don't see the value > of wasting more time to port what is like the 4th set of string tests. > Doesn't run during the build. > > 3. main/sal/qa/osl/security > Moved to Google Test, but doesn't compile as it needs the ancient > getForwardString() API from the obsolete testshl2 module. Doesn't run > during the build. > > 4. main/smoketestoo_native > Missing test/officeconnection.hxx from ages ago. Not clear whether we > still use the smoke test: on > https://wiki.openoffice.org/wiki/Test_Refactor there's a TODO "Convert > smoketestdoc & smoketestoo_native to JUnit 4 test cases" that's > crossed out with "Done!" appended. I emailed liuzhe (Zhe Liu) who did > that to ask what the status of smoketest is, but received no reply. > Does anybody know? > > 5. main/tools/qa > Won't link on Windows. Doesn't run during the build. > > 6. main/unoxml/test > Missing static libraries it depends on. Not integrated into gbuild > like the rest of the module. Doesn't run during the build. > > 7. main/writerfilter/qa/cppunittests > These tests don't even remotely compile, the entire odiapi seems to be > missing, QName is not a type any more. Looks like extremely old code. > Doesn't run during the build. > > 8. main/xmlsecurity/qa/certext > Missing test/officeconnection.hxx from ages ago, and needs > neon/ne_ssl.h from http://www.webdav.org/neon, an LGPL licensed > library. Doesn't run during the build. > > Since AOO builds I am happy to leave it at this, it would take weeks > to fix every last one of those tests and there's way more important > development to do. Thanks for your efforts in all this -- long overdo. From the list above, you are referring ONLY to the running of the Google tests I take it as your remark "AOO builds". I think item #8 would be our highest priority at the moment. > > Should I also commit some patches to the above issues that don't > completely fix the problems, but get them closer to working? For > example some I've ported to cppunit, but compiling or linking breaks > for other reasons; would it be ok if I commit that kind of change? Can you elaborate? IMO, nothing should be committed that breaks builds, especially as we are gearing up for 4.1.2. It would be difficult to test potential late additions to 4.1.2 if we have broken builds on our main branch. > > The following is now necessary for our unit tests: > * Hook up as many unit tests as possible into the build (not many currently are) > * Audit the use of OOO_SUBSEQUENT_CHECKS and remove it where it isn't necessary > > Regards > Damjan > -- -------------------------------------------- MzK “The journey of a thousand miles begins with a single step.” --Lao Tzu --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org For additional commands, e-mail: dev-help@openoffice.apache.org