[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xerces-c-dev
Subject:    Re: Xerces3.0 test suite status
From:       Alberto Massari <amassari () datadirect ! com>
Date:       2006-10-19 12:46:24
Message-ID: NTEXFE01utJLtosJ3Ih000003ac () NTEXFE01 ! bedford ! progress ! com
[Download RAW message or body]

Hi Jason,
I managed to build the stub DLL for Perl on Windows, and run the test 
suite against an instrumented build of Xerces (using Compuware DevPartner).

The short summary is that the test suite covers 39,4% of the lines 
and 42,6% of the methods of Xerces. I am attaching two CSV files 
listing the methods that are not called at all, and those that are 
called but execute less than 20% of their code.

A few quick things that could be done:
- do a parse operation on a schema-enabled document with 
setGenerateSyntheticAnnotations
- add an XML+XSD that have identity checking (xsd:unique/xsd:key/xsd:keyref)
- add an XML+XSD that make use of base64 data
- add an XML+XSD that make use of a regex pattern
- invoke parse using the other 3 XMLScanners

Alberto

At 10.01 13/10/2006 +0200, Alberto Massari wrote:
>Hi Jason,
>
>At 09.34 13/10/2006 +0530, Jason Stewart wrote:
>>Hey Alberto,
>>
>>On 10/12/06, Alberto Massari <amassari@datadirect.com> wrote:
>>>At 00.15 11/10/2006 +0530, Jason Stewart wrote:
>>> >Hey all,
>>> >
>>> >[..]
>>> >Finally, it would be great if we could use a coverage tool to see what
>>> >coverage we are getting in the test suite.
>>>
>>>Hi Jason,
>>>I tried using DevPartner Studio, but it works only with Visual C++
>>>and the Perl wrapper doesn't compile out of the box against the
>>>non-autoconf builds.
>>
>>it would be very cool if we could get that working - I have never had
>>a Visual C++ environment to do the testing. But if we could make it
>>work that would be super - it would especially mean that we could make
>>a binary available for windows folks.
>
>Ok, I'll see if I can get all the pieces from the makefile generated 
>on Linux...
>
>
>>>I found out that gcc has a coverage tool, gcov
>>>(http://gcc.gnu.org/onlinedocs/gcc/Gcov.html), that can be used to
>>>see the coverage data collected after an instrumented program has
>>>been executed.
>>>In order to profile the source, the options "-fprofile-arcs
>>>-ftest-coverage" need to be added to the compile flags. However, I
>>>tries this, and I get missing symbols from the link phase. Not being
>>>a master on gcc, maybe you can take it further....
>>
>>I believe it's as simple as including -lgcov on the link line. I'm on
>>an older slower machine, tho, so its hard for me to test because I'd
>>have to recompile the whole Xerces source...
>
>You are right, adding -lgcov makes the samples link. However, I am 
>stopped by two problems now:
>1) it looks that Handler/PerlEntityResolverHandler.i and 
>Handler/PerlNodeFilterCallbackHandler.i are missing from the repository
>2) Makefile.PL doesn't parse config.status correctly, and always 
>fails to get the values for CXX, CXXFLAGS, LDFLAGS, OPTIMIZE
>
>Alberto
>
>
>>I've also found an open source package 'lcov' that can html'ize the
>>output, so that it is easier to view the results.
>>
>>Cheers, jas.
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
>>For additional commands, e-mail: c-dev-help@xerces.apache.org
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
>For additional commands, e-mail: c-dev-help@xerces.apache.org

["coverage.zip" (application/zip)]

---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: c-dev-help@xerces.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]