Alexander KriegischandGitHub
744bf74767
* Sync Spock dependency versions * Now that Spock no longer depends on 'groovy-all', for the database test it was necessary to add 'groovy-sql'. * Make feature method names friendlier in unrolled DatabaseDrivenSpec * Make IncludeExcludeExtensionSpec print messages This way the user can verify visually that in-/excludes actually work as expected. * Upgrade Groovy 2.5.12 -> 2.5.13 * Slightly adjust README.adoc Change passive style "all feedback is appreciated" to active style "we appreciate all feedback".
75 lines
2.4 KiB
Groovy
75 lines
2.4 KiB
Groovy
/*
|
|
* Copyright 2010 the original author or authors.
|
|
*
|
|
* Licensed under the Apache License, Version 2.0 (the "License");
|
|
* you may not use this file except in compliance with the License.
|
|
* You may obtain a copy of the License at
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
* Unless required by applicable law or agreed to in writing, software
|
|
* distributed under the License is distributed on an "AS IS" BASIS,
|
|
* WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
* See the License for the specific language governing permissions and
|
|
* limitations under the License.
|
|
*/
|
|
|
|
import java.lang.annotation.*
|
|
|
|
import spock.lang.Specification
|
|
|
|
/**
|
|
* Shows how methods can be included and excluded from a spec run. For
|
|
* demonstration purposes, the configuration script's location is set
|
|
* programmatically in a static initializer. Usually, the configuration
|
|
* script's location would be set externally (via the same system property),
|
|
* or the configuration script would reside in one of the two default locations:
|
|
* <li>
|
|
* <ul><tt>SpockConfig.groovy</tt> on the class path</ul>
|
|
* <ul><tt>$user_home/.spock/SpockConfig.groovy</tt> on the file system</ul>
|
|
* </li>
|
|
*
|
|
* <p>Note that the configuration script referenced by the system property
|
|
* may either reside on the class path or on the file system (make sure to
|
|
* include the whole path).
|
|
*
|
|
* <p>What's not shown here is that filtering also works for classes.
|
|
* Whereas methods can only be filtered based on annotations, classes can
|
|
* also be filtered based on their base class.
|
|
*
|
|
* <p>If you directly want to see the effect of different Spock configurations,
|
|
* just run this spec from your IDE with an additional VM parameter
|
|
* <li>
|
|
* <ul><tt>-Dspock.configuration=IncludeFastConfig.groovy</tt> or</ul>
|
|
* <ul><tt>-Dspock.configuration=ExcludeSlowConfig.groovy</tt></ul>
|
|
* </li>
|
|
*
|
|
* <p>See also the two corresponding resource files provided with this spec.
|
|
*
|
|
* @since 0.4
|
|
*/
|
|
class IncludeExcludeExtensionSpec extends Specification {
|
|
@Fast
|
|
def "a fast method"() {
|
|
println "fast"
|
|
expect: true
|
|
}
|
|
|
|
@Slow
|
|
def "a slow method"() {
|
|
println "slow"
|
|
expect: true
|
|
}
|
|
|
|
def "a neither fast nor slow method"() {
|
|
println "neither fast nor slow"
|
|
expect: true
|
|
}
|
|
}
|
|
|
|
@Retention(RetentionPolicy.RUNTIME)
|
|
@Target(ElementType.METHOD)
|
|
@interface Fast {}
|
|
|
|
@Retention(RetentionPolicy.RUNTIME)
|
|
@Target(ElementType.METHOD)
|
|
@interface Slow {}
|