On 27 August 2012 18:14, Josef M. <
sicl...@googlemail.com> wrote:
> Hi Thomas, thx for your response. But i dont want to measure my own coverage
> of a test-project :/ i want the code coverage of the developers of selenium
> webdriver :/
Ok, then do something similar for the source code of WebDriver. It is
an open source project. All you have to do is build it and execute all
>
> Am Montag, 27. August 2012 18:04:02 UTC+2 schrieb Thomas Sundberg:
>>
>> On 27 August 2012 17:48, Josef M. <
sicl...@googlemail.com> wrote:
>> > Oh, it's about the tests written to test the functionality of selenium,
>> > usally unit-tests.
>> > here a short definition: "Code coverage is a measure used in software
>> > testing. It describes the degree to which the source code of a program
>> > has
>> > been tested."
>>
>> You could annotate your classes using Cobertura.[1] Then package your
>> annotated classes into a deployable archive, deploy it and execute
>> your test suite. This should create a file that records all
>> interactions with the code. If you then combine it with your source
>> code, you could see the lines of code that has been executed.
>>
>> I have done something similar when I measured the test coverage for a
>> multi module Maven project.[2]
>>
>> This approach would not involve Sonar, it would just involve Cobertura
>> (and Ant and Maven). But if you are writing a thesis, I assume that
>> fiddling a bit with Cobertura could be some additional stuff for your
>> thesis.
>>
>> HTH
>> Thomas
>>
>> [1]
http://cobertura.sourceforge.net/
>> [2]
>>
http://thomassundberg.wordpress.com/2012/02/18/test-coverage-in-a-multi-module-maven-project/
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Selenium Users" group.
> To post to this group, send email to
seleniu...@googlegroups.com.
> To unsubscribe from this group, send email to
>
selenium-user...@googlegroups.com.
> To view this discussion on the web visit