Hello,
If I can suggest it, talk to your boss about creating automation scripts by writing code rather than recording elements on the screen.
There are a lot of questions about the choice of working method:
1. how big application do you plan to cover with tests?
When working with keywordTest, you are using a very strong functionality called "NameMapping". Only selected elements should be added to this repository, not everything. Too large a NameMapping file will cause optimization problems in the future.
2. Maintaining and modifying the tests.
If your test scenarios are modified frequently, choose the scripting method with no keyword. It will be easier to maintain and create common libraries.
3. working together on the project and storing files in the repository.
By choosing the scripting method, it will be easier to divide the work into individual team members.
Searching for dynamic elements:
In TestComplete you can choose between different methods .Findxxx(),
One of them is the FindChild() method you mentioned.
An example from Javascript:
// variable
var object = Aliases.program.object;
// in the object you have in the variable you can search for the elementvar searched forObject = object.FindChild("property name", "property value", nesting)
// to the above-mentioned variable I'll save the object to be searched.
Inside the keyword test, Yo can actually write a function to perform some action.
If you open a tab called "Object browser" in TestComplete you will see all the elements that you can potentially map to Aliases and search by .Findxxx()
On the forum, we have already talked many times about topics related to starting work with TestComplete. Please check it:
https://community.smartbear.com/t5/TestComplete-Desktop-Testing/NameMapping-Alias-and-find-function/td-p/187593
https://community.smartbear.com/t5/TestComplete-Desktop-Testing/NameMapping-Alias-and-find-function/td-p/187593