Imported Keyword test does not work

Question

I am developing some autotest for a web site. All the tests will start from login page and login with user name and password. I planed to have to projects in the project suite: Project A to Project B. In Project A, I recorded a keyword test i to perform the login actions. In Project B, I imported the LoginTest of Project A. Then I created a keyword test (DashBoardTest) in Project B. The first step of the DashBoardTest is to run LoginTest.

I run the LoginTest in Project A, it works fine.

I run the DashBoard test in Project B, it launched the LoginPage but it can not find the Username input box and then it stops working.

This is a simple test to test the importing keyword test from one project to another. But it seems not working well.

What have I missed? I also notice, there is no "Reload" right click menu context. I am using Test Complete 12. How do I refresh the imported test?

pings · Accepted Answer

Thank you very much! I will start to review the 101.

tristaanogre · Answer

Import feature? Reload option?&nbsp; Namespace of NameMapping? I'm not sure what you're referencing.&nbsp; What I see on your screenshot is that the CU_LaunchLogin keyword test is shared with another project.&nbsp; So, I'm assuming you used the Add -&gt; Existing item to add that keyword test to project B.&nbsp;&nbsp;
&nbsp;
And yes, the "importing" references the imported test... FILE... So, there's a file on your drive called CU_LaunchLogin.tcKDT.&nbsp; When you did "add existing item", it linked that file to the new project.&nbsp; Renaming the file will break that link.&nbsp; If you change the file contents in one project, the update is automatic to the other.
&nbsp;
Here's some hints:1) Think of each "project" in TestComplete as if it is an application being developed in an IDE.&nbsp;&nbsp;
2) Each keyword test is a unit of code in that application
3) As in an application, if you change a unit of code in one application, all applications that use that same unit of code are automatically updated.
4) If you delete, remove, rename, or otherwise alter the file identification of the unit of code, that will "break" all those other applications unless you go to them and make the same updates
5) NameMapping, while not quite like a unit of code, follows the same rules.&nbsp; It is a file that, by default, "belongs" to a project.&nbsp; So, each project has it's own NameMapping file.&nbsp;&nbsp;As mentioned above, you can share the NameMapping between projects either by having them share the same file directly OR by manually merging the files as necessary.
&nbsp;
Again, please look into getting into the basic TestComplete 101 training.&nbsp; These are basic concepts to TestComplete covered in the training and in the documentation.

tristaanogre · Answer

One of two ways:1) Right click on the project and select "Add -&gt; Existing Item" and navigate to the NameMapping.tcNM from Project A and add it to Project B.&nbsp; The benefit of doing it this way is that, anytime you update object identification in either project, it will immediately update it in the other project.&nbsp; Requires Project B to not have a pre-existing NameMapping node... can be removed/deleted from the project if you desire to go this route.
&nbsp;
2) Right click on the NameMapping node of Project B and select "Merge" then navigate to the NameMapping file from Project A and complete the merge.&nbsp; The benefit of doing it this way is that you can isolate the NameMapping for the two projects so that changes in one don't affect the other.
&nbsp;
On a side note:Please find and view a TestComplete 101 webinar... you can attend one live or watch the recording of one.&nbsp; Either way, this will give you the basics of TestComplete.&nbsp; NameMapping is one of the core pieces of TestComplete and is the default behavior for object identification.&nbsp; Everything dealing with onscreen components references NameMapping.&nbsp; SO, get an understanding of NameMapping and you'll have a good portion of TestComplete known... and the webinars cover a good bit of this.

tristaanogre · Answer

The keyword test is probably referencing name mapped objects.&nbsp; So, you may have copied the keyword test to the new project but it is dependant upon the NameMapping scheme as well.&nbsp; Try sharing the name mapping between projects as well.

pings · Answer

I am new to Test Complete. How do I share the Name mapping?&nbsp;

pings · Answer

Thank you for your guidance. The importing feature is supposed to have just references to the imported tests. It seems like that the Name mapping object does not have the Namespace concept build in.&nbsp;&nbsp;By the way, how do I refresh the imported keyword test if it is modified or its name modified in the original project? How do I get that "Reload" menu option? The image shows what I see in my project. The CU_LaunchLogin is an imported test.

Forum Discussion

Imported Keyword test does not work

7 Replies

Related Content

Keyword test not working as Script test

importing function from javascript to keyword test

Expand Keyword test steps

How to propagate script changes back to the keyword test?

Import test cases

Recent Discussions

testcomplete feature Intelligent Quality Add Ons

SessionCreator /Timeout option not firing EventControl_OnTimeout

Object Browser does not display WPF DataGridCell Border

Issue with retrieving text from listbox items in desktop win32 application

Read data from Excel