Forum Discussion
- nebsta8 years agoContributor
tristaanogre that will teach me for not reading the question thoroughly! In that case I guess I would say the NameMapping. Despite the fact that I think there are a few improvements that could be done to make it a lot easier to maintain (e.g. links above) it does a good job of abstracting references to objects in tests to minimise rework required when the UI is changed.
- shankar_r8 years agoCommunity Hero
One thing i very admire and helped a lot is Project Variables that too table type.
Problem i had,
I have developed a data-driven framework which uses lot of excel sheets to get input. I'm having minimum of 10+ excels for input for a run. In this case i need to create 10+ DDT drivers to handle the scenarios which causes excel application not responding issue. Hence i was not able to run whole suite even a single time.
This given a bad point to management to think of automation feature in current project.
Solution i having now,
I used table type Project Variable to store all my excel sheet values in start of my execution and reused the Project Variable during the run. This got no pain excel application since the link between excel and TestComplete ended during the 1st few minutes setup.
Some more powerful features which doesn't need any explanation,
- Script Extension
- Extended Find in Name mapping
- Custom Object Mapping under Tools > Current Project Properties
I love most of the TestComplete features since it is ease our Automation process.
- AlexKaras8 years agoChampion Level 3
Hm-m-m...
I believe these are:-- Object Browser;
-- Aliasing;
-- Provided infrastructure (Log, Project Variables, Shared Mode, Test Items, etc.)
Related Content
- 12 years ago
- 2 years ago
Recent Discussions
- 4 days ago
- 4 days ago
- 7 days ago