[CLOV-373] Support for TestNG test optimization in Ant

Type: Suggestion
Resolution: Fixed
Fix Version/s: 2.4.2
Component/s: Ant Tasks
Labels:
None
Environment:
Ant

Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

TestNG test optimization is almost supported.

It seems the only thing missing, is the ability to specify an alternate snapshot file location, even if this means users are required to set <systemproperty> elements.

Otherwise - the testng task needs the {{ listeners="com.cenqua.clover.tasks.testng.CloverOptimizedTestSelector"
}} attribute set.

<testng
		    outputdir="${outdir}/${testresultsprefix}"
		    haltOnFailure="false"
            verbose="2"
            listeners="com.cenqua.clover.tasks.testng.CloverOptimizedTestSelector"
            groups="clover-optimized">
            <sysproperty key="clover.initstring" value="${clover.initstring}"/>
            <sysproperty key="clover.snapshot" value="${clover.snapshot}"/>

            <classpath refid="unittestpath"/>
            <classpath>
                <pathelement location="${outdir}/classes"/>
            </classpath>
            
            <classfileset dir="${outdir}/classes"/>  
        </testng>

The current means of configuring the CloverOptimizedTestSelector in TestNG is via System properties.

Document TestNG Support for Test Optimization

Closed

Unassigned

Katherine Yabut made changes - 19/Sep/2019 5:40 AM

Workflow	Original: JAC Suggestion Workflow [ 3342360 ]	New: JAC Suggestion Workflow 3 [ 3584853 ]
Status	Original: RESOLVED [ 5 ]	New: Closed [ 6 ]

Monique Khairuliana (Inactive) made changes - 13/Aug/2019 7:15 AM

Backlog Order (Obsolete)	Original: 3210000003
Workflow	Original: New Clover Workflow [ 897748 ]	New: JAC Suggestion Workflow [ 3342360 ]
Issue Type	Original: New Feature [ 2 ]	New: Suggestion [ 10000 ]
Status	Original: Closed [ 6 ]	New: Resolved [ 5 ]

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

Workflow

Original: Clover Workflow [ 895688 ]

New: New Clover Workflow [ 897748 ]

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

Workflow

Original: reviewflow [ 148102 ]

New: Clover Workflow [ 895688 ]

Marek Parfianowicz made changes - 03/Dec/2012 11:41 AM

Status

Original: Resolved [ 5 ]

New: Closed [ 6 ]

Nick made changes - 17/Dec/2008 5:24 AM

Description

Original: TestNG test optimization is almost supported.

It seems the only thing missing, is the ability to specify an alternate snapshot file location, even if this means users are required to set <systemproperty> elements.

Otherwise - the testng task needs the {{ listeners="com.cenqua.clover.tasks.testng.CloverOptimizedTestSelector"
}} attribute set.

{code}
<testng
outputdir="${outdir}/${testresultsprefix}"
haltOnFailure="false"
            verbose="2"
            listeners="com.cenqua.clover.tasks.testng.CloverOptimizedTestSelector"
            groups="${testng.group}">
            <sysproperty key="clover.initstring" value="${clover.initstring}"/>
            <sysproperty key="clover.snapshot" value="${clover.snapshot}"/>

            <classpath refid="unittestpath"/>
            <classpath>
                <pathelement location="${outdir}/classes"/>
            </classpath>

            <classfileset dir="${outdir}/classes"/>
        </testng>
{code}

The current means of configuring the CloverOptimizedTestSelector in TestNG is via System properties.

New: TestNG test optimization is almost supported.

It seems the only thing missing, is the ability to specify an alternate snapshot file location, even if this means users are required to set <systemproperty> elements.

Otherwise - the testng task needs the {{ listeners="com.cenqua.clover.tasks.testng.CloverOptimizedTestSelector"
}} attribute set.

{code}
<testng
outputdir="${outdir}/${testresultsprefix}"
haltOnFailure="false"
            verbose="2"
            listeners="com.cenqua.clover.tasks.testng.CloverOptimizedTestSelector"
            groups="clover-optimized">
            <sysproperty key="clover.initstring" value="${clover.initstring}"/>
            <sysproperty key="clover.snapshot" value="${clover.snapshot}"/>

            <classpath refid="unittestpath"/>
            <classpath>
                <pathelement location="${outdir}/classes"/>
            </classpath>

            <classfileset dir="${outdir}/classes"/>
        </testng>
{code}

The current means of configuring the CloverOptimizedTestSelector in TestNG is via System properties.

Nick made changes - 28/Nov/2008 4:33 AM

Resolution		New: Fixed [ 1 ]
Status	Original: Implemented [ 10025 ]	New: Resolved [ 5 ]

Nick made changes - 28/Nov/2008 4:33 AM

Description

Original: TestNG test optimization is almost supported.

It seems the only thing missing, is the ability to specify an alternate snapshot file location, even if this means users are required to set <systemproperty> elements.

Otherwise - the testng task needs the {{ listeners="com.cenqua.clover.tasks.testng.CloverOptimizedTestSelector"
}} attribute set.

{code}
<testng
outputdir="${outdir}/${testresultsprefix}"
haltOnFailure="false"
            verbose="2"
            listeners="com.cenqua.clover.tasks.testng.CloverOptimizedTestSelector"
            groups="${testng.group}">
            <sysproperty key="clover.initstring" value="${clover.initstring}"/>
            <classpath refid="unittestpath"/>
            <classpath>
                <pathelement location="${outdir}/classes"/>
            </classpath>

            <classfileset dir="${outdir}/classes"/>
        </testng>
{code}

New: TestNG test optimization is almost supported.

It seems the only thing missing, is the ability to specify an alternate snapshot file location, even if this means users are required to set <systemproperty> elements.

Otherwise - the testng task needs the {{ listeners="com.cenqua.clover.tasks.testng.CloverOptimizedTestSelector"
}} attribute set.

{code}
<testng
outputdir="${outdir}/${testresultsprefix}"
haltOnFailure="false"
            verbose="2"
            listeners="com.cenqua.clover.tasks.testng.CloverOptimizedTestSelector"
            groups="${testng.group}">
            <sysproperty key="clover.initstring" value="${clover.initstring}"/>
            <sysproperty key="clover.snapshot" value="${clover.snapshot}"/>

            <classpath refid="unittestpath"/>
            <classpath>
                <pathelement location="${outdir}/classes"/>
            </classpath>

            <classfileset dir="${outdir}/classes"/>
        </testng>
{code}

The current means of configuring the CloverOptimizedTestSelector in TestNG is via System properties.

Nick made changes - 24/Nov/2008 6:04 AM

Status

Original: Open [ 1 ]

New: Implemented [ 10025 ]

Nick created issue - 18/Nov/2008 4:18 AM

Assignee:: Michael Studman (Inactive)

Reporter:: Nick

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Created:: 18/Nov/2008 4:18 AM

Updated:: 19/Sep/2019 5:40 AM

Resolved:: 28/Nov/2008 4:33 AM

Details

Description

Attachments

Forms

Sub-Tasks

Activity

People

Dates