[CLOV-507] document distributed coverage configuration options

Type: Sub-task
Resolution: Fixed
Priority: Medium
Fix Version/s: 2.5
Affects Version/s: None
Component/s: Documentation, Test Optimization
Labels:
None

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.

Owen made changes - 07/Jul/2016 5:15 AM

Workflow

Original: New Clover Workflow [ 897732 ]

New: New Clover Workflow - Restricted [ 1474330 ]

Piotr Swiecicki made changes - 10/Jun/2015 10:53 AM

Workflow

Original: Clover Workflow [ 895621 ]

New: New Clover Workflow [ 897732 ]

Piotr Swiecicki made changes - 10/Jun/2015 10:30 AM

Workflow

Original: reviewflow [ 172086 ]

New: Clover Workflow [ 895621 ]

Edwin Dawson [Atlassian] made changes - 23/Apr/2009 5:00 AM

Resolution		New: Fixed [ 1 ]
Status	Original: In Progress [ 3 ]	New: Closed [ 6 ]

Edwin Dawson [Atlassian] made changes - 20/Apr/2009 6:26 AM

Status

Original: Open [ 1 ]

New: In Progress [ 3 ]

Edwin Dawson [Atlassian] made changes - 20/Apr/2009 6:26 AM

Assignee

New: Edwin Dawson [Atlassian] [ edawson ]

Nick made changes - 20/Apr/2009 1:00 AM

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.

Nick made changes - 20/Apr/2009 12:52 AM

Description

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

<distributedConfiguration> accepts the following 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*)

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.

Nick made changes - 20/Apr/2009 12:33 AM

Description

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

<distributedConfiguration> accepts the following attributes:

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

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

<distributedConfiguration> accepts the following 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*)

Nick made changes - 19/Apr/2009 12:08 PM

Component/s		New: Documentation [ 12211 ]
Description		New: For distributed per-test coverage to be enabled, the nested <distributedConfiguration/> element of clover-setup and clover-instr must be specified: <distributedConfiguration> accepts the following attributes: * name the name of this configuration * port the port to the test JVM should listen on * host the host name the test JVM should bind to * timeout (number) the amount of time(ms) to wait before a connection attempt will fail * numClients (number) the number of clients that need to connect to the test server before the tests will continue * retryPeriod (number) the amount of time (ms) to wait before attempting to reconnect in the advent of a network failure

Assignee:: Edwin Dawson [Atlassian]

Reporter:: Nick

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 19/Apr/2009 12:02 PM

Updated:: 23/Apr/2009 5:00 AM

Resolved:: 23/Apr/2009 5:00 AM

Estimated:

Remaining:

Logged:

Not Specified

Details

Description

Attachments

Forms

Activity

People

Dates

Time Tracking