Uploaded image for project: 'Clover'
  1. Clover
  2. CLOV-373

Support for TestNG test optimization in Ant

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 2.4.2
    • Ant Tasks
    • None
    • Ant

    • 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.

          1.
          		 Document TestNG Support for Test Optimization Sub-task Closed Unassigned

              mstudman Michael Studman (Inactive)
              npellow Nick
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: