Contributions
Re: Windows showing as dlg and not a shell
I wrote a blog post on it last week. https://leesainsbury.wordpress.com/2015/10/16/how-to-create-a-basic-automation-framework-with-testcomplete/ Esentially it is just one big script that holds all of your functions etc and all of the other tests reference this script.2.7KViews0likes0CommentsRe: Windows showing as dlg and not a shell
I'm not sure I have an answer to the direct root of the problem, however I'd suggest creating a framework in your project regardless in case the software under test changes for any reason. If the developers change something in the software which affects your name mapping you would have to update every test that contains that mapped object. If you create a framework you can just change the framework and your tests will reflect this.2.8KViews0likes2CommentsRe: Unable to Identify Devexpress control only during runtime
It does sound like bad identification properties. Grab the old path to the control and then update the controls path and see if they differ. If so there's some property which is changing during runtime. If that is the case what object properties is the name mapping looking for?3.8KViews0likes2CommentsRe: Constant Name Mapping issues
Yah its coded in Delphi and C++, the joys! I guess it will be a long process to get used to all the oddities of Delphi and TestComplete. There's been so many already its been hard to progress as quickly as I would have liked to. Unfortunately I don't have many Developers that are willing to spend some time helping! Thanks a lot for the help :)2.8KViews0likes0CommentsRe: aqobject verifying element name
When you say "better" way what do you hope to achieve? Performance is not an issue and I wouldn't see coding standards to be an issue at all. The reason I ask is because we need to think about why we are spending the time changing something that already works as intended.3.3KViews0likes3CommentsRe: aqobject verifying element name
Well if the field that displays the object is different and the object property is different then you could either use a switch case statement or an if else both with logging. If you want specific logging for each output I would assume that this is one of the best ways. Its not really that much of a problem since once you've written the framework you just need to change the name and the logging to whatever you want. Plus an if statement will typically execute in about a second so, it'll be quite fast :)3.3KViews0likes5CommentsRe: aqobject verifying element name
Just use an if statement with a log or event message so you can write whatever you like in the log. For example: If (this.mainelement.WPFObject.wText = "John" ) Then Call Log.Event("This ComboBox contains the word John") Else Call Log.Error("This ComboBox does not contain the word John") End If Hopefully this is along the right path. You can also do this using the Wizard using the If and Else statements with a Log.Event/Error.3.3KViews0likes7CommentsRe: Constant Name Mapping issues
Unbeliavble, it doesn't happen once I remove the WndCaption from the Name Mapping properites. What do you mean by invisible control character? I'd just like to understand what was going on a little better. But in any case thank you for the response :) Edit: Ah a non printing character, why would that happen?2.9KViews0likes2CommentsConstant Name Mapping issues
Hey guys/girls, I'm having constant issues with TestComplete mapping the same object as a new object, and I have no idea why it is doing this. If you have a look at the screenshot attached, TImpactEntryEdit has been mapped, WndCaption should not look for a specific value and I have even added a wildcard at the end of TImpactEntryEdit, however all of a sudden it is now looking for TImpactEntryEdit2. Does anybody have any leads as to why this might be happening? This has been happening quite often for me on many of my applications forms. I'm testing a VCL desktop application. Thanks in advance for any information :)Solved2.9KViews0likes4Comments