As the subject suggests our test team are looking to automate testing using Selenium, which works well on non-webMethods systems.
However I’ve been told that when deploying webMethods the page/portlet id’s used by the internal webMethods DB change, thus rendering the automated test scripts invalid after every deploy!
Does anybody know of a way to correct this behaviour?
Selenium (or more recently WebDriver) have flexible selectors that can easily compensate for the dynamic nature of the first segment of those ids.
For example, if you want to select some table element with an id that ends with the text “_id_sufix” in a WebDriver test, you can use a CSS selector that looks something like this: