Why do my ClassMaps no longer work after upgrading SilkTest or applying a hot fix?
Prior to the release of SilkTest 13 the only means to implement Class Maps for Custom Controls, when using the Open Agent; was to manually modify the plugin.xml file for the relevant techdomain.
The reason these class maps no longer work after upgrading SilkTest; is because the upgrade process overwrites the folder containing the modified version plugin.xml file, with a newer one that is now being used by the Open agent.
The upgrade does not delete the modified copy of plugin.xml, so this should still exist somewhere within the following directory; depending on which tech-domain you are testing, and which SilkTest build was running when the class maps were applied:
C:\Program Files (x86)\Silk\SilkTest\ng\agent\plugins
For example if you were running the release build of SilkTest 14(6504) when you mapped some custom controls to standard Win32 control types; then you would have to modify the plugin.xml file in the following directory:
C:\Program Files (x86)\Silk\SilkTest\ng\agent\plugins\com.borland.fastxd.techdomain.win32.agent_126.96.36.19904
After applying Hotfix 03 for SilkTest 14 the following folder is created and the Open Agent now reads the plugin.xml file from this directory, where the class mappings do not exist:
C:\Program Files (x86)\Silk\SilkTest\ng\agent\plugins\com.borland.fastxd.techdomain.win32.agent_188.8.131.5231
You can reapply the class maps by copying the changes in the original plugin.xml to the new one. However please ensure that you restart the Open Agent so that the changes are applied.
Finally, since the release of SilkTest 13 the recommended approach for implementing Class Maps is to use the new 'Manage Custom Controls' feature. This allows you to create custom classes for unsupported controls; which will not be affected by upgrading your version of SilkTest.