UI Test Automation is being practiced by all client and primary key to script and execute test automation successfully lies with stable and unique component ID for all UI components. PTC R&D also having Selenium Test Automation and it's being exercised for product validation. Stability of Selenium Test automation and UI Test automation tool in general completely depends on robust DOM structure with well defined and stable UI Component ID as a backbone.
In our current implementation we have Selenium Test Automation Implemented as part of BDD Testing Framework and it's being used for monthly Product Enhancement Release validation. It's working very efficiently in Windchill 11.2 release. However with Windchill 12 release ,many of UI components unique ID has been changed and affected stability of test automation. It resulted in maintenance overhead to update the scripts as per updated UI Component ID. Proposal here is:-
Support stable well defined UI component ID and avoid any unnecessary component ID update which can impact client who are having UI Test Automation in place
Development practice to support UI Test Automation by supporting strcutured and stable component ID in backend
Provide component ID update as part of release documentation so that the maintenance effort can be minimized for end consumers having UI Test Automation.