> you can do whatever feels right for a given case Too bad you can't use whatever specification language feels right. Spock only provides Apache Groovy, with i

> you can do whatever feels right for a given case Too bad you can't use whatever specification language feels right. Spock only provides Apache Groovy, with its tacky syntax hacks like long strings for function names, block labels having special meanings based on their name, or the OR and LOR operators being used for drawing tables in the code. In the past when software has provided Groovy for writing specs, they eventually provide an alternative when Groovy's shortfalls become obvious, e.g. Kotlin for Gradle [1], or the Declarative Pipeline Syntax [2] for Jenkins. [1]: https://docs.gradle.org/5.0/userguide/kotlin_dsl.html https://docs.gradle.org/5.0/userguide/kotlin_dsl.html [2]: https://jenkins.io/blog/2016/12/19/declarative-pipeline-beta https://jenkins.io/blog/2016/12/19/declarative-pipeline-beta