[jira] Created: (MCOBERTURA-114) Instrumenting Deployment Artifacts (major site doc enhancement and small plugin enhancement)

Instrumenting Deployment Artifacts (major site doc enhancement and small plugin enhancement)
--------------------------------------------------------------------------------------------

                 Key: MCOBERTURA-114
                 URL: http://jira.codehaus.org/browse/MCOBERTURA-114
             Project: Maven 2.x Cobertura Plugin
          Issue Type: Improvement
    Affects Versions: 2.4
         Environment: any

            Reporter: James Carpenter
         Attachments: additionalMavenDocs.pdf, CoberturaDiagrams.pdf, deploymentArtifactInstrumentation.patch

It is occasionally useful to measure the code coverage for manual and/or
automated tests which run against a test environment.(Not to be confused with
measuring code coverage of unit tests executed automatically by the
build system.) For example, you may have a set of automated regression
tests written using JMeter, Selenium, etc. which for some reason or
another are not appropriate to run as part of the maven build.

The primary difficulty in supporting the above use case is understanding
what needs done, and then to a limited extent configuring Maven appropriately.
To that end I have added a new "Instrumenting a Deployment Artifact" section
to the Maven Cobertura plugin's site documentation.  I have attached a PDF
showing the html rendered version of the enhanced documentation
(source documentation file is in the usual apt format).

In addition to the documentation enhancements, I have extended the instrument goal
to support registering a module's cobertura.ser file as an attached artifact.
This turns out to significantly clean up the child modules of a multi-module
project, which would otherwise be cluttered with build-helper plugin configuration
details.

The attached patch file contains all of my changes.  I look forward to a
release in the near future which contains these changes, provided they
are deemed acceptable by the project maintainers.



--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

    [ http://jira.codehaus.org/browse/MCOBERTURA-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196927#action_196927 ]

James Carpenter commented on MCOBERTURA-114:
--------------------------------------------

I have also included some scans of hand-drawn diagrams I drew to complement the text.
The documentation text in the patch does not currently link to or otherwise include the hand-drawn diagrams.  I created
the hand-drawn diagrams for use inside my company after I had finished creating the patch.

> Instrumenting Deployment Artifacts (major site doc enhancement and small plugin enhancement)
> --------------------------------------------------------------------------------------------
>
>                 Key: MCOBERTURA-114
>                 URL: http://jira.codehaus.org/browse/MCOBERTURA-114
>             Project: Maven 2.x Cobertura Plugin
>          Issue Type: Improvement
>    Affects Versions: 2.4
>         Environment: any
>            Reporter: James Carpenter
>         Attachments: additionalMavenDocs.pdf, CoberturaDiagrams.pdf, deploymentArtifactInstrumentation.patch
>
>
> It is occasionally useful to measure the code coverage for manual and/or
> automated tests which run against a test environment.(Not to be confused with
> measuring code coverage of unit tests executed automatically by the
> build system.) For example, you may have a set of automated regression
> tests written using JMeter, Selenium, etc. which for some reason or
> another are not appropriate to run as part of the maven build.
> The primary difficulty in supporting the above use case is understanding
> what needs done, and then to a limited extent configuring Maven appropriately.
> To that end I have added a new "Instrumenting a Deployment Artifact" section
> to the Maven Cobertura plugin's site documentation.  I have attached a PDF
> showing the html rendered version of the enhanced documentation
> (source documentation file is in the usual apt format).
> In addition to the documentation enhancements, I have extended the instrument goal
> to support registering a module's cobertura.ser file as an attached artifact.
> This turns out to significantly clean up the child modules of a multi-module
> project, which would otherwise be cluttered with build-helper plugin configuration
> details.
> The attached patch file contains all of my changes.  I look forward to a
> release in the near future which contains these changes, provided they
> are deemed acceptable by the project maintainers.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email