Uploaded image for project: 'Clover'
  1. Clover
  2. CLOV-391 Allow per-test coverage to be recorded across multiple JVMs
  3. CLOV-507

document distributed coverage configuration options

XMLWordPrintable

      For distributed per-test coverage to be enabled, the nested <distributedConfiguration/> element of clover-setup and clover-instr must be specified.

      The simplest and quickest means to have distributed coverage collected is to add the <distributedcoverage/> element to clover-setup (or clover-instr) and then set the clover.server system property on the JVM running your tests:

      Step 1 Configure Clover with distributed coverage.

      <clover-setup>
  <distributedcoverage/>
</clover-setup>

      Step 2 Set the clover.server system property on the test JVM

       <junit fork="true" forkmode="once" showoutput="true" printsummary="true">
                <sysproperty key="clover.server" value="true"/>
               ....
</junit>

      NB: forkmode of perTest is currently unsupported.

      <distributedConfiguration> accepts the following optional attributes:

      • name the name of this configuration (tcp-config)
      • port the port the test JVM should listen on (1198)
      • host the host name the test JVM should bind to (localhost)
      • timeout (number) the amount of time(ms) to wait before a connection attempt will fail (5000)
      • numClients (number) the number of clients that need to connect to the test server before the tests will continue (0)
      • retryPeriod (number) the amount of time (ms) to wait before attempting to reconnect in the advent of a network failure (1000)

      NB: all attributes are optional.

            [CLOV-507] document distributed coverage configuration options

            Owen made changes -
            Workflow Original: New Clover Workflow [ 897732 ] New: New Clover Workflow - Restricted [ 1474330 ]
            Piotr Swiecicki made changes -
            Workflow Original: Clover Workflow [ 895621 ] New: New Clover Workflow [ 897732 ]
            Piotr Swiecicki made changes -
            Workflow Original: reviewflow [ 172086 ] New: Clover Workflow [ 895621 ]
            Edwin Dawson [Atlassian] made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]

            Edwin Dawson [Atlassian] added a comment -

            I've addressed these points:

            http://confluence.atlassian.com/display/CLOVER/(hidden+draft)+Working+with+Distributed+Applications

            Edwin Dawson [Atlassian] added a comment - I've addressed these points: http://confluence.atlassian.com/display/CLOVER/(hidden+draft)+Working+with+Distributed+Applications

            Nick added a comment - - edited

            Good start at the draft.

            Some points:

            the heading:

            Attributes for the <distributedConfiguration> Element

            makes no sense where it is. It needs to come after an introduction, or at least when the distributedConfiguration element is mentioned.
            That element also needs to appear as a nested element for the clover-setup and clover-instr tasks.

            The other way of setting up distributed coverage is mentioned: http://jira.atlassian.com/browse/CLOV-499 .
            forkMode attribute of junit task is described here: http://ant.apache.org/manual/OptionalTasks/junit.html

            Also, one of the major features users can take advantage of with this, is Test Optimization.

            Nick added a comment - - edited Good start at the draft. Some points: the heading: Attributes for the <distributedConfiguration> Element makes no sense where it is. It needs to come after an introduction, or at least when the distributedConfiguration element is mentioned. That element also needs to appear as a nested element for the clover-setup and clover-instr tasks. The other way of setting up distributed coverage is mentioned: http://jira.atlassian.com/browse/CLOV-499 . forkMode attribute of junit task is described here: http://ant.apache.org/manual/OptionalTasks/junit.html Also, one of the major features users can take advantage of with this, is Test Optimization.

            Edwin Dawson [Atlassian] added a comment - - edited

            Draft:
            http://confluence.atlassian.com/display/CLOVER/(hidden+draft)+Working+with+Distributed+Applications

            Also, added the <distributedConfiguration> element to these pages:

            http://confluence.atlassian.com/display/CLOVER/(hidden+draft)+clover-setup
            http://confluence.atlassian.com/display/CLOVER/(hidden+draft)+clover-instr

            Edwin Dawson [Atlassian] added a comment - - edited Draft: http://confluence.atlassian.com/display/CLOVER/(hidden+draft)+Working+with+Distributed+Applications Also, added the <distributedConfiguration> element to these pages: http://confluence.atlassian.com/display/CLOVER/(hidden+draft)+clover-setup http://confluence.atlassian.com/display/CLOVER/(hidden+draft)+clover-instr
            Edwin Dawson [Atlassian] made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Edwin Dawson [Atlassian] made changes -
            Assignee New: Edwin Dawson [Atlassian] [ edawson ]
            Nick made changes -
            Description Original: For distributed per-test coverage to be enabled, the nested <distributedConfiguration/> element of clover-setup and clover-instr must be specified.

            The simplest and quickest means to have distributed coverage collected is to add the <distributedcoverage/> element to clover-setup (or clover-instr) and then set the clover.server system property on the JVM running your tests:

            *Step 1* Configure Clover with distributed coverage.
            {code}
            <clover-setup>
              <distributedcoverage/>
            </clover-setup>
            {code}

            *Step 2* Set the clover.server system property on the test JVM
            {code}
             <junit fork="true" forkmode="once" showoutput="true" printsummary="true">
                            <sysproperty key="clover.server" value="true"/>
                           ....
            </junit>
            {code}
            *NB*: forkmode of perTest is currently unsupported.


            <distributedConfiguration> accepts the following optional attributes:

            * name the name of this configuration (*tcp-config*)
            * port the port the test JVM should listen on (*1198*)
            * host the host name the test JVM should bind to (*localhost*)
            * timeout (number) the amount of time(ms) to wait before a connection attempt will fail (*5000*)
            * numClients (number) the number of clients that need to connect to the test server before the tests will continue (*0*)
            * retryPeriod (number) the amount of time (ms) to wait before attempting to reconnect in the advent of a network failure (*1000*)

            NB: all attributes are optional.


            		New: For distributed per-test coverage to be enabled, the nested <distributedConfiguration/> element of clover-setup and clover-instr must be specified.

            The simplest and quickest means to have distributed coverage collected is to add the <distributedcoverage/> element to clover-setup (or clover-instr) and then set the clover.server system property on the JVM running your tests:

            *Step 1* Configure Clover with distributed coverage.
            {code}
            <clover-setup>
              <distributedcoverage/>
            </clover-setup>
            {code}

            *Step 2* Set the {{clover.server}} system property on the test JVM
            {code}
             <junit fork="true" forkmode="once" showoutput="true" printsummary="true">
                            <sysproperty key="clover.server" value="true"/>
                           ....
            </junit>
            {code}
            *NB*: forkmode of perTest is currently unsupported.


            <distributedConfiguration> accepts the following optional attributes:

            * name the name of this configuration (*tcp-config*)
            * port the port the test JVM should listen on (*1198*)
            * host the host name the test JVM should bind to (*localhost*)
            * timeout (number) the amount of time(ms) to wait before a connection attempt will fail (*5000*)
            * numClients (number) the number of clients that need to connect to the test server before the tests will continue (*0*)
            * retryPeriod (number) the amount of time (ms) to wait before attempting to reconnect in the advent of a network failure (*1000*)

            NB: all attributes are optional.


              edawson Edwin Dawson [Atlassian]
              npellow Nick
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Estimated:
                  Original Estimate - 2h
                  2h
                  Remaining:
                  Remaining Estimate - 2h
                  2h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified