Test Groovy code

It is the customer's responsibility to ensure that all groovy-based code extensions are thoroughly tested before they are initially put in production, and then again with each upgrade to a major release.

Any signature changes for a patch or point release should be listed under the Critical Action Required section of the release notes, so that complete Groovy testing is not required for each incremental upgrade, though it's recommended if possible.

Confirming the version of Groovy supported with your version of N4

Enter the following code in the Script Runner window and run it:

import org.codehaus.groovy.runtime.InvokerHelper
class GroovyHello {
public String execute()
{
return GroovySystem.getVersion()
}
}

The Result window will display the compatible groovy version. For instance for N4 3.6 it will display 2.1.9.

Testing before initial deployment

If testing a code extension before deploying in production for the first time, you need to test it individually from the Script Runner window (Administration DBA Script Runner).

Testing after an upgrade

With each upgrade you need to test your groovy thoroughly before pushing the upgrade to production. Thorough testing requires that you do the following:

  1. Compile all Groovy code to check for errors. See Testing Groovy in a new release (on page 1)

  1. Test each Groovy code extension individually to check for runtime errors that wouldn't be caught by manual compilation. See Testing Groovy code extensions individually (on page 1).

  2. Test all web services. See  Test Web services using Groovy code (on page 1).

  3. Test code extensions for Notices, Gate and EDI. Errors in these extensions will not be caught by manual compilation.

If you have not used a Groovy hook, such as a code extension or Groovy plug-in, to invoke your code, you will not be able to take advantage of the testing tools available. See Use a Code Extension type or a Groovy plug-in (on page 1).

In This Section