You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Mike Matrigali <mi...@sbcglobal.net> on 2012/02/21 20:31:23 UTC
missing link for emma reports.
I was interested in identifying untested areas of the code. It looks
like emma runs are running successfully and mostly being reported
against trunk at:
http://dbtg.foundry.sun.com/derby/test/coverage/
And drilling down to latest jdk17 run at following also seems to work:
http://dbtg.foundry.sun.com/derby/test/coverage/coverage/sol/suitesAll20100402/suitesAll.coveragereport.html
I am hoping to get to a detail where I could identify untested
routines/lines. I think it might be at the following "all classes" link
from above page but get an error trying to use that link. I have not
looked at this for a long time, so not sure if it has ever worked
publicly or not.:
http://dbtg.foundry.sun.com/derby/test/coverage/coverage/sol/suitesAll20100402/index.html
gives:
Not Found
The requested URL
/derby/test/coverage/coverage/sol/suitesAll20100402/index.html was not
found on this server
Re: missing link for emma reports.
Posted by Mike Matrigali <mi...@sbcglobal.net>.
>
> You can drill down by clicking the package/class name. Am I
> misunderstanding your question?
>
> For instance, at package level:
> http://dbtg.foundry.sun.com/derby/test/coverage/_files/1a.html
> And at the class level:
> http://dbtg.foundry.sun.com/derby/test/coverage/_files/d2.html
>
>
thanks, i just did not realize the link was there. This now has
everything I was looking for.
Re: missing link for emma reports.
Posted by Kristian Waagan <kr...@oracle.com>.
On 22.02.2012 18:28, Mike Matrigali wrote:
> Knut Anders Hatlen wrote:
>> Knut Anders Hatlen <kn...@oracle.com> writes:
>>
>>> dag.wanvik@oracle.com (Dag H. Wanvik) writes:
>>>
>>>> Mike Matrigali <mi...@sbcglobal.net> writes:
>>>>
>>>>> I am hoping to get to a detail where I could identify untested
>>>>> routines/lines. I think it might be at the following "all classes"
>>>>> link from above page but get an error trying to use that link. I
>>>>> have
>>>>> not looked at this for a long time, so not sure if it has ever worked
>>>>> publicly or not.:
>>>>> http://dbtg.foundry.sun.com/derby/test/coverage/coverage/sol/suitesAll20100402/index.html
>>>>>
>>>> Not sure what's happening here. When I run emma in my sandbox I can
>>>> indeed use these links. I believe Knut set this up on the test
>>>> machines, I'm sure he can figure out what's missing tomorrow.
>>> The date in the URL indicates it's a two year old test run, so it
>>> probably doesn't tell much about the present state of the trunk in any
>>> case. :)
>>>
>>> I have set up a nightly test coverage run, but it's not published
>>> anywhere right now. For some reason, the report generation frequently
>>> fails with:
>>>
>>> java.io.UTFDataFormatException: malformed input around byte 52
>>> at java.io.DataInputStream.readUTF(DataInputStream.java:656)
>>> at java.io.DataInputStream.readUTF(DataInputStream.java:564)
>>> at
>>> com.vladium.emma.data.ClassDescriptor.readExternal(ClassDescriptor.java:171)
>>> at com.vladium.emma.data.MetaData.readExternal(MetaData.java:228)
>>> at
>>> com.vladium.emma.data.DataFactory.readEntry(DataFactory.java:770)
>>> at
>>> com.vladium.emma.data.DataFactory.mergeload(DataFactory.java:461)
>>> at com.vladium.emma.data.DataFactory.load(DataFactory.java:56)
>>> at
>>> com.vladium.emma.report.ReportProcessor._run(ReportProcessor.java:175)
>>> at com.vladium.emma.Processor.run(Processor.java:54)
>>> at
>>> com.vladium.emma.report.reportCommand.run(reportCommand.java:130)
>>> at emma.main(emma.java:40)
>>>
>>> I'll see if I can publish the reports in the cases where they are
>>> generated successfully.
>>
>> An updated report is available here:
>> http://dbtg.foundry.sun.com/derby/test/coverage/
>>
> thanks. That is a great upper level report. Is there any generated
> report/data that would allow me to tell which classes, methods,
> blocks, lines are not covered? Obviously lines would be a huge amount
> of data. I think classes and methods would be a great start at
> pointing us at what new testing we should do.
You can drill down by clicking the package/class name. Am I
misunderstanding your question?
For instance, at package level:
http://dbtg.foundry.sun.com/derby/test/coverage/_files/1a.html
And at the class level:
http://dbtg.foundry.sun.com/derby/test/coverage/_files/d2.html
--
Kristian
Re: missing link for emma reports.
Posted by Mike Matrigali <mi...@sbcglobal.net>.
Knut Anders Hatlen wrote:
> Knut Anders Hatlen <kn...@oracle.com> writes:
>
>> dag.wanvik@oracle.com (Dag H. Wanvik) writes:
>>
>>> Mike Matrigali <mi...@sbcglobal.net> writes:
>>>
>>>> I am hoping to get to a detail where I could identify untested
>>>> routines/lines. I think it might be at the following "all classes"
>>>> link from above page but get an error trying to use that link. I have
>>>> not looked at this for a long time, so not sure if it has ever worked
>>>> publicly or not.:
>>>> http://dbtg.foundry.sun.com/derby/test/coverage/coverage/sol/suitesAll20100402/index.html
>>> Not sure what's happening here. When I run emma in my sandbox I can
>>> indeed use these links. I believe Knut set this up on the test
>>> machines, I'm sure he can figure out what's missing tomorrow.
>> The date in the URL indicates it's a two year old test run, so it
>> probably doesn't tell much about the present state of the trunk in any
>> case. :)
>>
>> I have set up a nightly test coverage run, but it's not published
>> anywhere right now. For some reason, the report generation frequently
>> fails with:
>>
>> java.io.UTFDataFormatException: malformed input around byte 52
>> at java.io.DataInputStream.readUTF(DataInputStream.java:656)
>> at java.io.DataInputStream.readUTF(DataInputStream.java:564)
>> at com.vladium.emma.data.ClassDescriptor.readExternal(ClassDescriptor.java:171)
>> at com.vladium.emma.data.MetaData.readExternal(MetaData.java:228)
>> at com.vladium.emma.data.DataFactory.readEntry(DataFactory.java:770)
>> at com.vladium.emma.data.DataFactory.mergeload(DataFactory.java:461)
>> at com.vladium.emma.data.DataFactory.load(DataFactory.java:56)
>> at com.vladium.emma.report.ReportProcessor._run(ReportProcessor.java:175)
>> at com.vladium.emma.Processor.run(Processor.java:54)
>> at com.vladium.emma.report.reportCommand.run(reportCommand.java:130)
>> at emma.main(emma.java:40)
>>
>> I'll see if I can publish the reports in the cases where they are
>> generated successfully.
>
> An updated report is available here:
> http://dbtg.foundry.sun.com/derby/test/coverage/
>
thanks. That is a great upper level report. Is there any generated
report/data that would allow me to tell which classes, methods, blocks,
lines are not covered? Obviously lines would be a huge amount of data.
I think classes and methods would be a great start at pointing us at
what new testing we should do.
Re: missing link for emma reports.
Posted by Knut Anders Hatlen <kn...@oracle.com>.
Knut Anders Hatlen <kn...@oracle.com> writes:
> dag.wanvik@oracle.com (Dag H. Wanvik) writes:
>
>> Mike Matrigali <mi...@sbcglobal.net> writes:
>>
>>> I am hoping to get to a detail where I could identify untested
>>> routines/lines. I think it might be at the following "all classes"
>>> link from above page but get an error trying to use that link. I have
>>> not looked at this for a long time, so not sure if it has ever worked
>>> publicly or not.:
>>> http://dbtg.foundry.sun.com/derby/test/coverage/coverage/sol/suitesAll20100402/index.html
>>
>> Not sure what's happening here. When I run emma in my sandbox I can
>> indeed use these links. I believe Knut set this up on the test
>> machines, I'm sure he can figure out what's missing tomorrow.
>
> The date in the URL indicates it's a two year old test run, so it
> probably doesn't tell much about the present state of the trunk in any
> case. :)
>
> I have set up a nightly test coverage run, but it's not published
> anywhere right now. For some reason, the report generation frequently
> fails with:
>
> java.io.UTFDataFormatException: malformed input around byte 52
> at java.io.DataInputStream.readUTF(DataInputStream.java:656)
> at java.io.DataInputStream.readUTF(DataInputStream.java:564)
> at com.vladium.emma.data.ClassDescriptor.readExternal(ClassDescriptor.java:171)
> at com.vladium.emma.data.MetaData.readExternal(MetaData.java:228)
> at com.vladium.emma.data.DataFactory.readEntry(DataFactory.java:770)
> at com.vladium.emma.data.DataFactory.mergeload(DataFactory.java:461)
> at com.vladium.emma.data.DataFactory.load(DataFactory.java:56)
> at com.vladium.emma.report.ReportProcessor._run(ReportProcessor.java:175)
> at com.vladium.emma.Processor.run(Processor.java:54)
> at com.vladium.emma.report.reportCommand.run(reportCommand.java:130)
> at emma.main(emma.java:40)
>
> I'll see if I can publish the reports in the cases where they are
> generated successfully.
An updated report is available here:
http://dbtg.foundry.sun.com/derby/test/coverage/
--
Knut Anders
Re: missing link for emma reports.
Posted by Knut Anders Hatlen <kn...@oracle.com>.
dag.wanvik@oracle.com (Dag H. Wanvik) writes:
> Mike Matrigali <mi...@sbcglobal.net> writes:
>
>> I am hoping to get to a detail where I could identify untested
>> routines/lines. I think it might be at the following "all classes"
>> link from above page but get an error trying to use that link. I have
>> not looked at this for a long time, so not sure if it has ever worked
>> publicly or not.:
>> http://dbtg.foundry.sun.com/derby/test/coverage/coverage/sol/suitesAll20100402/index.html
>
> Not sure what's happening here. When I run emma in my sandbox I can
> indeed use these links. I believe Knut set this up on the test
> machines, I'm sure he can figure out what's missing tomorrow.
The date in the URL indicates it's a two year old test run, so it
probably doesn't tell much about the present state of the trunk in any
case. :)
I have set up a nightly test coverage run, but it's not published
anywhere right now. For some reason, the report generation frequently
fails with:
java.io.UTFDataFormatException: malformed input around byte 52
at java.io.DataInputStream.readUTF(DataInputStream.java:656)
at java.io.DataInputStream.readUTF(DataInputStream.java:564)
at com.vladium.emma.data.ClassDescriptor.readExternal(ClassDescriptor.java:171)
at com.vladium.emma.data.MetaData.readExternal(MetaData.java:228)
at com.vladium.emma.data.DataFactory.readEntry(DataFactory.java:770)
at com.vladium.emma.data.DataFactory.mergeload(DataFactory.java:461)
at com.vladium.emma.data.DataFactory.load(DataFactory.java:56)
at com.vladium.emma.report.ReportProcessor._run(ReportProcessor.java:175)
at com.vladium.emma.Processor.run(Processor.java:54)
at com.vladium.emma.report.reportCommand.run(reportCommand.java:130)
at emma.main(emma.java:40)
I'll see if I can publish the reports in the cases where they are
generated successfully.
--
Knut Anders
Re: missing link for emma reports.
Posted by "Dag H. Wanvik" <da...@oracle.com>.
Mike Matrigali <mi...@sbcglobal.net> writes:
> I am hoping to get to a detail where I could identify untested
> routines/lines. I think it might be at the following "all classes"
> link from above page but get an error trying to use that link. I have
> not looked at this for a long time, so not sure if it has ever worked
> publicly or not.:
> http://dbtg.foundry.sun.com/derby/test/coverage/coverage/sol/suitesAll20100402/index.html
Not sure what's happening here. When I run emma in my sandbox I can
indeed use these links. I believe Knut set this up on the test
machines, I'm sure he can figure out what's missing tomorrow.
Thanks,
Dag
>
> gives:
>
>
> Not Found
>
> The requested URL
> /derby/test/coverage/coverage/sol/suitesAll20100402/index.html was not
> found on this server