Developers creating new Preference Sets should thoroughly test them before deploying them to a production environment.
This should include verifying each preference is tested to assure that changes on the server are applied on the client. This can only be done with an end-to-end test:
- Verifying the template has the correct preference name. The smallest error in the name of the preferences will result in the preference not being recognized by the client.
- Verify that all values, or at least a representative sample of values, for each preference is tested and produces the correct client behavior.
- Verify that the correct behavior occurs on the client when the Policy Type is loaded and no subPolicies have been created.
Parent topic: Creating Eclipse Preference Sets with the Policy Type Editor: XPD621