Breaking Changes

Version 8.0.0+

Groovy was updated to 4.0.7

See Groovy 4 Update section for details.

Deprecated SrSpecification class removed

Authors of script plugins may be used to writing tests which extend the deprecated com.onresolve.scriptrunner.canned.common.admin.SrSpecification class. This class has been removed. Authors of tests for their scripts should extend the spock.lang.Specification class directly. Tests should still be picked up by Test Runner built-in script as normal.

Version 7.0.0+

Custom Search Fields was updated in 7.7.0

The Search Extractors feature was removed and replaced with Custom Search Fields in ScriptRunner for Confluence release 7.7.0. Please refer to the Custom Search Fields documentation for more information.

Groovy was updated to 3.0.12

See the Groovy 3 Update section in the 7.0.0 Release Notes for details. 

Spock was updated to 2.0

As part of upgrading to Groovy 3, we had to update Spock because there is no Groovy 3 compatible version of Spock 1.3, which was used in ScriptRunner 6. 

You can use Spock to write and run unit tests within ScriptRunner. It is unlikely that tests written by ScriptRunner users would use parts of Spock 2.0 that contain breaking changes. However, if you maintain tests for your scripts, you should explore the breaking changes listed in the release notes for Spock 2.0.

JUnit 4 removal

Although it wasn't advertised in the documentation, it was possible to write and run unit tests using JUnit 4 in ScriptRunner 6. Spock 2.0 is based on JUnit Platform, not JUnit 4, so JUnit 4 tests will no longer work inside ScriptRunner.

If you wrote any tests using JUnit 4, you will need to rewrite them using Spock 2.0.

Version 6.17.0+ 

IE

The last ScriptRunner version compatible with IE11 is 6.17.0. Do not update ScriptRunner past this version if using IE11.