spenserjames
New Contributor
Joined 16 years ago
User Profile
User Widgets
Contributions
Re: NameMapping Issues When Moving from Windows XP to 7
Hi Jared, It turns out that the problematic controls were from DevExpress, and the debug info was not included because the libraries were so large. Once the debug info was included, the objects were correctly recorded as having the WndClass property. Although this doesn't fix the previously recorded tests, it won't be a problem in the future. Thanks!1KViews0likes0CommentsRe: NameMapping Issues When Moving from Windows XP to 7
Hi Jared, Most of the objects are VCLObjects, but the ones I'm having problems with are recognized as Windows (e.g. "TcxCustomComboBoxInnerEdit"). The 'Delphi and C++Builder Open Applications Support' plug-in is already installed.1KViews0likes0CommentsNameMapping Issues When Moving from Windows XP to 7
Hello, I recently recorded some tests on an application my company is developing using Windows XP. The tests work fine, but when I attempted to run the same tests on the same application in Windows 7, TestComplete couldn't recognize several of the text editing objects. More specifically, the application is programmed in Delphi, and TestComplete originally mapped the problem objects to both "ClassName" and "ObjectIdentifier" properties. When the test is run in Windows 7, the "ObjectIdentifier" property does not correctly identify the object, so TestComplete thinks it isn't there. If the "ObjectIdentifier" property is removed, everything works fine. Is there a way to remove the "ObjectIdentifier" property from all the objects in a project or project suite, without going through and manually deleting each one? Also, is there a way to specify that TestComplete shouldn't map to the ObjectIdentifier property at all during future recordings? Thanks! Spenser11KViews0likes5Comments