QTP学习资料归总01

讲解01.QTP与QC/TD整合

1.整合总体讲解

整合QTP跟QC（Quantity Center）是一件不错的选择，其会有下面一些好处：

　　1> 如果本身是使用TD来做测试管理工具的话就可以方便测试用例跟测试脚本对应，方便管理。当然也方便Issue了。

　　2>用来存储并管理脚本。将脚本放在QC上就可以让团队编写使用脚本更为方便有效还可以进行脚本版本控制。

　　3> 可以方便组织脚本运行。可以方便组织哪些脚本在设定时间内在哪台机子上去跑脚本，跑完脚本后还将测试结果发送到相应负责人手中。

　　看起来他们整合好处也不少，但要整合好也不容易，特别是需要费点时间去设置host机（用来跑脚本的机子）。废话少说，开始整合工作。

　　首先当然是要装个QC（旧版本的叫Merqury Test Direct），怎样安装就是题外话就不说了。安装运行QC后就可以设置QTP连接QC了。这个也简单输入QC的访问URL然后选择相应的Project那些……

　　此时应该就可以将QTP脚本放到QC上去了。接下来就是QTP 与QC/TD整合的最大好处体现了，不过也是最费时间设置的时候了。将脚本就到QC上后就可以在QC的客户端（浏览器）调用QTP并执行脚本。这个时候要设置的主要是两个方面。

　　一个是QC客户端如假设机器名称为PC_QC，即是用来访问QC的机器。这里需要安装一个插件，这个一般情况下在你的QTP压缩包中有个"TD plugin"文件夹，里面就是这个插件了，如果没有也不紧要，可以下载。 步骤如下：工a）通过浏览器打开QC后，在主页面中根据链接其他 Mercury Quality Center 加载项—— QuickTest Professional 加载项进入下载页面，单击“下载 Quality Center 8。2 的加载项”进行下载并在您的客户端计算机上安装此加载项。b）下载并安装QC连通性加载项。进入加载项主页面，根据链接Mercury Quality Center连通性进入下载页面，下载并安装。c）它要求新启动，必须重新启动后才可用。 d）注意事项：QTP跟QC的版本必须是适用的，插件版本当然也要一致了，在下载处有说明。然后是安装时必须是以管理员身分安装的。

　　上面即是服务端（相对于运行脚本时用来调用的机子而言的服务器）的设置。接下来就是设置客户端（用来被调用用于执行脚本的机子）。首先这个机子必须已经安装了QTP（没有QTP的话用什么来跑???呵呵），然后设置QTP允许外部程序执行：Tools—Option Run标签页给"Allow other Mercury products to run tests and components"打勾。或许也可以选上"Submit a defect to Qualiyt Center for each failed step"。其实你也会奇怪怎么这台机器就允许别的机子来访问（通过qtp remote agent）呢?用什么用户名密码呢?首先你两机子要在同一上局域网内了（不然就太不安全了），然后客户端那些端口必须是打开的，然后放开一些特殊用户的权限。这个设置比较麻烦也是很多搞QTP整合QC不成功的地方。我设置时也试过很多网上的偏方但就是不行，后来才google到了官方处方，虽然有点麻烦，但是可行。由于较长，我将转载到下一篇。

　　如果都设置好了的话就可以要服务端即是上面设置好的机器PC_QC上打开QC，然后选择要执行的脚本并为其选择用来执行的机子即客户端，然后在设定的时间上执行脚本了。

 

2.具体QTP客户端配置讲解：

Product:
TestDirector 8.0
TestDirector for Quality Center 8.2
TestDirector for Quality Center 9.0
DB(s):
Not Relevant

Topics:
Integrating with Astra QuickTest / QuickTest Professional
Integrating with WinRunner
Error Messages
Integrating with QuickTest Professional
Integrating with VAPI-XP
Integrating with Business Process Testing
OS:
Windows XP

Creation Date:
14 Aug 2004  Last Modified Date:
18 Sep 2006

 

--------------------------------------------------------------------------------

Problem Descrīption: Error: "RPC server is unavailable" or "Access is denied" during remote execution of automated scrīpts on Windows XP SP2

The user receives the following error message when executing a automated scrīpt remotely after installing Windows XP SP2:

"The RPC server is unavailable."

or

"Access is denied."

Executing the scrīpt locally works correctly.

Diagnosis: Security changes in Windows XP SP2 have blocked the remote agent of the testing tool from being launched. This caused the failure of the automated scrīpt execution.

Note: Windows XP SP2 is supported with TestDirector 8.0 SP2 and TestDirector for Quality Center 8.2 and above only. For more information on supported operating systems, please refer to the links below:
Problem ID 44879 - What are the system requirements for TestDirector for Quality Center 9.0
Problem ID 36167 - What are the system requirements for Quality Center 8.2
Problem ID 25963 - What are the system requirements for TestDirector 8.0

 

--------------------------------------------------------------------------------

Solution: Change the DCOM permissions on the Windows XP SP2 client to allow for remote execution

Notes:

The security changes suggested below should be applied by your System Administrator. Please contact Microsoft Support if you have questions regarding changes in DCOM securities caused by installing Windows XP SP2.

If you disable the firewall installed with Windows XP SP2, you do not need to apply the steps in Part II below. However, a utility (CPT33502C.zip) has been created to automate the steps for opening the ports outlined in Part II.

Part III - VI can be applied automatically by running the attached batch file included in CPT33502B.zip. You will need to extract the contents of this zip file to a temp directory and execute the SetWRandQTPIPDCOM.bat file. The batch file (CPT33502B.zip) will use the dcomperm.exe (CPT33502D.zip) provided by Microsoft to update the DCOM properties of the remote agents for WR, QTP, BPT, System Test, and VAPI-XP. Your system administrator should be able to run this batch file across the network to update each Windows XP SP2 machine. If you apply the batch file, you do not need to implement the steps in Part III - VI below.
The following is the manual process for openning the firewall ports and modifying the DCOM properties for WR, QTP, BPT, System Test, and VAPI-XP.

Part I:
Add both machines into the same domain. For the domain users logged into both machines, add these domain users to the Local Administrators group on the QTP/WR machine. This is required for Windows to authenticate the remote user executing the tests against the DCOM objects.

Part II:
On the Testing Tool client machine configure Windows Firewall to allow Port 135 for DCOM:
1. Select Start -> Control Panel -> Windows Firewall.
2. Navigate to the Exceptions tab.
3. Configure the Remote Agent to be allowed under "Programs and Services." Configuration should be done for each testing tools as given below:

WinRunner Remote Agent (path: <System Drive>:/Program Files/Common Files/Mercury Interactive/WR_Remoter/wrrmtsrv.exe)
QuickTest Professional Remote Agent (path: <System Drive>:/Program Files/Mercury Interactive/QuickTest Professional/bin/AQTRmtAgent.exe)
Execution Agent for Business Process Testing (path: <System Drive>:/Program Files/Common Files/Mercury Interactive/TD2000_80/bp_exec_agent.exe)
4. Click on <Add Port> and add the DCOM TCP port 135 to the Exceptions list.
Note: The WR remote agent is a DCOM object and requires port 135 to work. The list of "Port Assignments for Commonly-Used Services" is provided in the URL below:
http://www.microsoft.com/resourc ... t/cnfc_por_SIMW.asp

Part III:
Modify DCOM Security Properties:
1. Select Start -> Run and enter dcomcnfg.
2. Navigate to Console Root -> Component Services -> Computers -> My Computer.
Note: If Windows Security Alert dialog window appears, click on <Ask me later> or <Unblock>.
3. Right-click on My Computers and select "Properties."
4. Navigate to the Default Properties tab.
5. Make sure the Default Impersonation Level is "Identify."
6. Click <Apply>.
7. Navigate to the Defualt COM Security tab.
8. Under Access Permissions, click on <Edit Limits>. The Access Permission dialog window appears.
9. Click on <Add>. The Select Users or Groups dialog windows appear.
10. Click on <Advanced>.
11. Click on <Find Now>.
12. Add the following groups and users from the local machine (below is an example screenshot):

Administrator
Administrators
Authenticated User
Anonymous Logon
Everyone
Interactive
Network
System

13. Click <OK>.
14. Add the following groups and users from the domain:

<tdomain user logged into the QTP/WR box>
<domain user logged into the TD client box executing the remote execution>

15. Click <OK>.
16. Give "Local Access" and "Remote Access" permissions to the groups and users.
17. Click <OK>.
18. Under Access Permissions, repeat steps 9-17 for <Edit Default>.
19. Under Launch and Activation Permissions, click on <Edit Limits>. The Launch Permission dialog window appears.
20. Repeat steps 9-15.
21. Enable "Local Launch," "Remote Launch," "Local Activation," and "Remote Activation" permissions to the groups and users.
22. Click <OK>.
23. Repeat steps 20-22 for <Edit Default>.
Part IV: (for QTP only)
1. While still in the Component Services window, navigate to Console Root -> Component Services -> Computers -> My Computer -> DCOM Config.
2. Look for the following.

AQTRmtAgent
QuickTest Professional Automation
TlpRmtServer

3. For each of these DCOM applications, right click and select <Properties>.
4. Under the Identity tab, select <The Interactive User>. This will allow the DCOM application to authenticate the process against the logged in Windows user and run the process in that security context.
5. Next, go to the Security tab.
6. For both the <Launch and Activation Permissions> and <Access Permissions>, select <Use Default>. This will use the Default security settings as we did in Part III.
7. Click Apply, then OK to commit the changes.
8. Now, you are ready to run a remote execution test with QTP.
Example Screenshot of the Security Configuration (see word attachment)
Part V: (for WR only)
1. While still in the Component Services window, navigate to Console Root -> Component Services -> Computers -> My Computer -> DCOM Config.
2. Look for the following:

{0B171F02-F204-11D0-9398-0080C837F11F}
Wrun Document

3. For each of these DCOM applications, right click and select <Properties>.
4. Under the Identity tab, select <The Interactive User>. This will allow the DCOM application to authenticate the process against the logged in Windows user and run the process in that security context.
5. Next, go to the Security tab.
6. For both the <Launch and Activation Permissions> and <Access Permissions>, select <Use Default>. This will use the Default security settings as we did in Part III.
7. Click Apply, then OK to commit the changes.
8. Now, you are ready to run a remote execution test with WR.
Part VI: (For System Test, BPT, and VAPI-XP)
Repeat the procedure outlined in Part V above but replace the WR Application ID in step 2 with the appropriate one for each of the remote agent listed below:

Vapi-XP object
{CD70EDCE-7777-11D2-9509-0080C82DD192}

Business Process Testing object
{6A03829E-EC39-4802-A631-3841484EFBE3}

System Test Remote Agent
{1B78CAE4-A6A8-11D5-9D7A-000102E1A2A2}

Notes:

If you have not configured the Remote Agent to be allowed under "Programs and Services," a Windows Security Alert message will appear while running a test remotely. Click <Unblock> to resolve this problem. The next time you execute an automated scrīpt, the warning will not appear.
If after performing all the described steps and you still receive "The RPC server is unavailable" message, create some shared folder anywhere on the Testing Tool machine.
Below is a list of supported Mercury's Testing Tools on Windows XP SP2:

TestDirector Version Testing Tool Testing tool versions
TestDirector for Quality Center 8.2 QuickTest Professional 8.2
  WinRunner 8.0, 8.2
  Business Process Testing 8.2
TestDirector 8.0 SP2 QuickTest Professional 8.2
  WinRunner 8.0, 8.2