-
Notifications
You must be signed in to change notification settings - Fork 26
using_groovy
This article documents the current best practices for using Groovy in toolkit development.
All Groovy class should be declared as statically type checked. Do this by annotating classes with the @TypeChecked annotation.
@TypeChecked
public class MyClass {
}
This provides no extra safety when working in Intellij. Intellij has its own way of indicating a problem. It is a bit subtle but it does help. This annotation is processed by the Groovy compiler used by Maven. So if you are having problems with your code and think it might be a type problem, run a Maven build on your module.
There are some Groovy facilities that are not available when using @TypeChecked.
The only way to understand what is usable and what is not is to build code and occasionally
run the module build from Maven. This will give you the feedback.
Toolkit
Downloads
Installing Toolkit
Configuring Toolkit for Imaging Tests
Reporting Toolkit Installation Problems
Environment
Test Session
Conformance Test Tool
Writing Conformance Tests
Overview of Imaging Tests
Test Context Definition
Launching Conformance Tool from Gazelle
Inspector
External Cache
Support Tools
Test Organization
Configuring Test Kits
Managing Multiple Test Kits
SAML Validation against Gazelle
Renaming Toolkit
Toolkit API
Managing system configurations
Configuring Toolkit for Connectathon
Developer's blog