Uploaded image for project: 'Clover'
  1. Clover
  2. CLOV-1256 as a developer I'd like to instrument tests written in the Spock framework
  3. CLOV-1362

Add Spock test name patterns in default test detector

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: Medium Medium
    • 3.3.0
    • None
    • Instrumentation
    • None

      Clover's default test detector should properly recognize Spock-framework test classes and which methods are test ones and which are helper ones. We shall not see stuff like this in the test summary:

      Tests 	Started 	Status 	Time (secs) 	Message
OpsWiseJobQueryTestSpec. 	12 mar 10:32:50 	PASS 	0 	     // BAD
OpsWiseJobQueryTestSpec.$spock_feature_1_0 	12 mar 10:32:49 PASS 	0,001 	// OK, but use original name
OpsWiseJobQueryTestSpec. 	12 mar 10:32:49 	PASS 	0 	     // BAD
OpsWiseJobQueryTestSpec.setup 	12 mar 10:32:49 	PASS 	0,009        // BAD

            [CLOV-1362] Add Spock test name patterns in default test detector

            Owen made changes -
            Workflow Original: New Clover Workflow [ 897464 ] New: New Clover Workflow - Restricted [ 1474007 ]
            Piotr Swiecicki made changes -
            Workflow Original: Clover Workflow [ 896355 ] New: New Clover Workflow [ 897464 ]
            Piotr Swiecicki made changes -
            Workflow Original: reviewflow [ 553958 ] New: Clover Workflow [ 896355 ]
            Marek Parfianowicz made changes -
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Marek Parfianowicz made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: To be reviewed [ 10026 ] New: Resolved [ 5 ]
            Marek Parfianowicz made changes -
            Status Original: Implemented [ 10025 ] New: To be reviewed [ 10026 ]
            Marek Parfianowicz made changes -
            Status Original: Open [ 1 ] New: Implemented [ 10025 ]
            Marek Parfianowicz made changes -
            Description Original: Clover's default test detector should properly recognized Spock-framework test classes and which methods are test ones and which are helper ones. We shall not see stuff like this in the test summary:

            {noformat}
            Tests Started Status Time (secs) Message
            OpsWiseJobQueryTestSpec. 12 mar 10:32:50 PASS 0 // BAD
            OpsWiseJobQueryTestSpec.$spock_feature_1_0 12 mar 10:32:49 PASS 0,001 // OK, but use original name
            OpsWiseJobQueryTestSpec. 12 mar 10:32:49 PASS 0 // BAD
            OpsWiseJobQueryTestSpec.setup 12 mar 10:32:49 PASS 0,009 // BAD
            {noformat}
            		New: Clover's default test detector should properly recognize Spock-framework test classes and which methods are test ones and which are helper ones. We shall not see stuff like this in the test summary:

            {noformat}
            Tests Started Status Time (secs) Message
            OpsWiseJobQueryTestSpec. 12 mar 10:32:50 PASS 0 // BAD
            OpsWiseJobQueryTestSpec.$spock_feature_1_0 12 mar 10:32:49 PASS 0,001 // OK, but use original name
            OpsWiseJobQueryTestSpec. 12 mar 10:32:49 PASS 0 // BAD
            OpsWiseJobQueryTestSpec.setup 12 mar 10:32:49 PASS 0,009 // BAD
            {noformat}
            Marek Parfianowicz made changes -
            Description Original: Clover's default test detector should properly recognized Spock-framework test classes and which methods are test ones and which are helper ones. We shall not see stuff like this in the test summary:

            {noformat}
            Tests Started Status Time (secs) Message
            OpsWiseJobQueryTestSpec. 12 mar 10:32:50 PASS 0 // BAD
            OpsWiseJobQueryTestSpec.$spock_feature_1_0 12 mar 10:32:49 PASS 0,001 // OK, but use original name
            OpsWiseJobQueryTestSpec. 12 mar 10:32:49 PASS 0 // BAD
            OpsWiseJobQueryTestSpec.setup 12 mar 10:32:49 PASS 0,009 // BAD
            {noformat}
            		New: Clover's default test detector should properly recognized Spock-framework test classes and which methods are test ones and which are helper ones. We shall not see stuff like this in the test summary:

            {noformat}
            Tests Started Status Time (secs) Message
            OpsWiseJobQueryTestSpec. 12 mar 10:32:50 PASS 0 // BAD
            OpsWiseJobQueryTestSpec.$spock_feature_1_0 12 mar 10:32:49 PASS 0,001 // OK, but use original name
            OpsWiseJobQueryTestSpec. 12 mar 10:32:49 PASS 0 // BAD
            OpsWiseJobQueryTestSpec.setup 12 mar 10:32:49 PASS 0,009 // BAD
            {noformat}
            Marek Parfianowicz made changes -
            Description Original: Clover's default test detector should properly recognized Spock-framework test classes and which methods are test ones and which are helper ones. We shall not see stuff like this in the test summary:

            {noformat}

            {noformat}
            		New: Clover's default test detector should properly recognized Spock-framework test classes and which methods are test ones and which are helper ones. We shall not see stuff like this in the test summary:

            {noformat}
            Tests Started Status Time (secs) Message
            OpsWiseJobQueryTestSpec. 12 mar 10:32:50 PASS 0 // BAD
            OpsWiseJobQueryTestSpec.$spock_feature_1_0 12 mar 10:32:49 PASS 0,001 // OK, but use original name
            OpsWiseJobQueryTestSpec. 12 mar 10:32:49 PASS 0 // BAD
            OpsWiseJobQueryTestSpec.setup 12 mar 10:32:49 PASS 0,009 // BAD
            {noformat}
            Marek Parfianowicz created issue -

              mparfianowicz Marek Parfianowicz
              mparfianowicz Marek Parfianowicz
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: