Mark_Küpper
Occasional Contributor
Joined 13 years ago
User Profile
User Widgets
Contributions
Auto-Wait timeout for all conditions of the "If Object"-Operation
The Auto-Wait timeout is usually applied to all keyword operations to wait for objects that are not immediately available. I do think, that the "If Object"-Operation is - or rather should be - a special case. As it is now, the operation does honour the Auto-Wait value when the check condition is set to "Exists". However, when it is set to "Visibility" or "Enabled", "If Object" does immediately process the state. It would be nice if "If Object" would use the Auto-Wait timeout regardless of the configured check condition. Alternatively, a timeout parameter for the other conditions would be a nice-to-have.TC 12.60: NameMapping editor does not show nested properties anymore
Hello, I have come across this issue, while evaluating TestComplete V.12.60: The NameMapping view allows to manually choose the properties of mapped items. In TC V.12.50 that included properties that where present in underlying objects. In TC V.12.60 however such objects are no longer shown in the list of available properties. They are still shown in the Object Browser and if a mapped item does already possess a nested identification criteria from earlier TC versions, the recognition does still work. So, the question is: Could this be a new issue or am I just missing a new option or behavior change? A Screenshot for clarification: RegardsRe: Support references to NameMappings of other projects
Yes, I second that! Being able to reference (multiple) NameMapping-Files in conjunction with the projects own NameMapping would be great for collaborate work in general and not only for specific scenarios (different apps). I see that this request is "Selected for Development" for over one and a half year; is there any news on how things are going? Is there a rough ETA?Renaming a Keyword-Test/Script should rename the corresponding reference as well
I have a ProjectSuite with multiple projects in which keyword-test-routines of one project are referenced in multiple other projects. If an original keyword-routine is renamed, there is no other way but to remove and then readd the references after which all usages of these references in actual tests have to be found and replaced with the renamed references as well - needless to say, that this is always a quite hideous task. It would be very helpful if renaming a keyword/script would also rename all references and all places where they are used.Re: DevExpress 17.1 support
I have just discovered this entry in the changelog of TC V.12.31: > > Developer Express controls 17.1.3 for Windows Forms. > That sounds great! And while DX has already upped their build number to 17.1.4, it remains to be seen if that is an actual problem. Looking forward to try out the new TC version.Target Object based context menu items in more operations
The 'On-Screen Action'-Keyword-Operation has some very handy context menu items regarding its target object: These menu items would be very useful in other operations as well, like: 'If Object', 'Call Object Method', 'Find Object', 'Menu Action'.
