quick way to automatically map all UI objects in a form

Hi,



Right-click your object in the Name Mapping editor and click the 'Map Child Objects' context menu item. You'll get the dialog which allows you to select which children to map and map them automatically.

Thanks for the quick reply. I also have several other questions:

1. when recording the test, testcomplete automatically creates the sequence of activities recorded during the test, so why do we need the scripts? how does changing scripts affects the course of the test and vice versa?

2. I input a login credential in a login form, and then after clicking log in button, the app will call a pop up window. there's a slight delay between clicking button and the pop up appears. the next step in the test after logging in is to input additional credentials in the mentioned pop up window. This is where I got "object is missing". Is it because testcomplete tries to send keyboard input to the popup window when it's not appeared yet? could you please explain this case and the solution?

3. In another popup window, I use the alias in an If....Then statement during test. The funny thing is sometimes the test will say "Unexpected window" and the entire test stops with an error. When I toggled a breakpoint, the name of the object is something like Sys.Process("abc").VCLObject("AddForm") instead of Aliases.App.AddForm. Can you explain this and what's the solution to prevent this problem?

4. Could you please explain the extended find? Is it for object that has variable parents or an object like tree that may have variable content?

5. How do I add keyword test from other project? in some cases, I have what you say "Common Repository" where common tests can be embedded so I don't have to "reinvent the wheel".

Thank you very much.

Any help anyone? thanks

Hi,



Actually, when you have additional questions not related to the thread's original topic, it is better to create new threads instead of posting them all in the same one. This allows tracking them all more efficiently.



Anyway:

1. Scripts and KD tests are just defferent ways to represent actions. Changing a script affects your test flow in the way you script it. It doesn't do anything 'by itself' - whatever you write in your script will be executed if you call it. See the Different Ways of Testing help topic.

2. You need to wait for your new window to appear.

3. See the Handling Unexpected Windows help topic for information on what this means and on how to deal with it.

4. Extended Find is explained in the Using Extended Search Criteria for Mapped Object Identification help topic.

5. You need to share your KD test among projects where you want it used.