-
Notifications
You must be signed in to change notification settings - Fork 26
Environment
The Environment is a part of the Toolkit External Cache that defines these elements:
- Codes Configuration (codes.xml)
- Certificate used by the Test Client when initiating a SOAP transaction
- Private Test Kits configured to match the Codes Configuration (see Configuring Test Kits).
There is always an Environment named default which matches the Test Kit internal to Toolkit. This default Environment always has a codes.xml file. Everything else is optional.
Environment definitions are stored in the External Cache. The default Environment is found at
environment/default/
and its Codes Configuration at
environment/default/codes.xml
If it has a certificate then this content is added
environment/default/keystore/keystore
environment/default/keystore/keystore.properties
where keystore is a Java Keystore and keystore.properties is a Java properties file containing the password to the Keystore file. Example content looks like
keyStorePassword=changeit
New Codes Configurations and Environments are created manually.
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