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

New tutorial for test optimization

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 2.4.2
    • Documentation
    • None

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

      We've decided to have a separate tutorial for Clover's Test Optimization functionality.

      The build_optimized.xml file gets the following lines added at the top:

       <taskdef resource="cloverlib.xml" classpath="${clover.jar}"/>
    <taskdef resource="cloverjunitlib.xml" classpath="${clover.jar}"/>
    <clover-env/>

    <property name="clover.ordering" value="default"/>
    <!-- @ordering: optional; values "failfast" or "normal"; default: "failfast"; -->
    <property name="clover.optimize" value="false"/>
    <!-- Enable/Disable optimization -->
    <property name="clover.fullrunevery" value="10"/>
    <!-- Determine how many builds between full builds. -->

      and the test.run target changes to:

          <target name="test.run" depends="test.compile" description="Runs the tests">
        <mkdir dir="${test.result}"/>
        <junit fork="yes" printsummary="true">
            <classpath refid="testbuild.classpath"/>
            <formatter type="xml"/>
            <batchtest fork="yes" todir="${test.result}">
                <clover-optimized-testset fullrunevery="${clover.fullrunevery}" optimize="${clover.optimize}"
                                          ordering="${clover.ordering}">
                    <fileset dir="${test.src}" includes="**/*Test.java"/>
                </clover-optimized-testset>
            </batchtest>
        </junit>
    </target>

            [CLOV-358] New tutorial for test optimization

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3342769 ] New: JAC Suggestion Workflow 3 [ 3585196 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: New Clover Workflow - Restricted [ 1474787 ] New: JAC Suggestion Workflow [ 3342769 ]
            Assignee Original: Edwin Dawson [Atlassian] [ edawson ]
            Issue Type Original: Task [ 3 ] New: Suggestion [ 10000 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Owen made changes -
            Workflow Original: New Clover Workflow [ 897632 ] New: New Clover Workflow - Restricted [ 1474787 ]
            Piotr Swiecicki made changes -
            Workflow Original: Clover Workflow [ 895373 ] New: New Clover Workflow [ 897632 ]
            Piotr Swiecicki made changes -
            Workflow Original: reviewflow [ 147083 ] New: Clover Workflow [ 895373 ]
            Edwin Dawson [Atlassian] made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            Edwin Dawson [Atlassian] made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Nick made changes -
            Fix Version/s New: 2.4.2 [ 14322 ]
            Fix Version/s Original: 2.4 [ 13971 ]
            Nick made changes -
            Description Original: We've decided to have a separate tutorial for Clover's Test Optimization functionality.

            The build_optimized_completed.xml file gets the following lines added at the top:
            {code}
             <taskdef resource="cloverlib.xml" classpath="${clover.jar}"/>
                <taskdef resource="cloverjunitlib.xml" classpath="${clover.jar}"/>
                <clover-env/>

                <property name="clover.ordering" value="default"/>
                <!-- @ordering: optional; values "failfast" or "normal"; default: "failfast"; -->
                <property name="clover.optimize" value="false"/>
                <!-- Enable/Disable optimization -->
                <property name="clover.fullrunevery" value="10"/>
                <!-- Determine how many builds between full builds. -->
            {code}

            and the test.run target changes to:
            {code}
                <target name="test.run" depends="test.compile" description="Runs the tests">
                    <mkdir dir="${test.result}"/>
                    <junit fork="yes" printsummary="true">
                        <classpath refid="testbuild.classpath"/>
                        <formatter type="xml"/>
                        <batchtest fork="yes" todir="${test.result}">
                            <clover-optimized-testset fullrunevery="${clover.fullrunevery}" optimize="${clover.optimize}"
                                                      ordering="${clover.ordering}">
                                <fileset dir="${test.src}" includes="**/*Test.java"/>
                            </clover-optimized-testset>
                        </batchtest>
                    </junit>
                </target>
            {code}             		New: We've decided to have a separate tutorial for Clover's Test Optimization functionality.

            The build_optimized.xml file gets the following lines added at the top:
            {code}
             <taskdef resource="cloverlib.xml" classpath="${clover.jar}"/>
                <taskdef resource="cloverjunitlib.xml" classpath="${clover.jar}"/>
                <clover-env/>

                <property name="clover.ordering" value="default"/>
                <!-- @ordering: optional; values "failfast" or "normal"; default: "failfast"; -->
                <property name="clover.optimize" value="false"/>
                <!-- Enable/Disable optimization -->
                <property name="clover.fullrunevery" value="10"/>
                <!-- Determine how many builds between full builds. -->
            {code}

            and the test.run target changes to:
            {code}
                <target name="test.run" depends="test.compile" description="Runs the tests">
                    <mkdir dir="${test.result}"/>
                    <junit fork="yes" printsummary="true">
                        <classpath refid="testbuild.classpath"/>
                        <formatter type="xml"/>
                        <batchtest fork="yes" todir="${test.result}">
                            <clover-optimized-testset fullrunevery="${clover.fullrunevery}" optimize="${clover.optimize}"
                                                      ordering="${clover.ordering}">
                                <fileset dir="${test.src}" includes="**/*Test.java"/>
                            </clover-optimized-testset>
                        </batchtest>
                    </junit>
                </target>
            {code}
            Edwin Dawson [Atlassian] made changes -
            Summary Original: New tutorial for build optimization New: New tutorial for test optimization

              Unassigned Unassigned
              npellow Nick
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: