QTP automated testing integrated QC - to build the directory structure

QC directory structure of the server-based, carried out to build directory.

If we can use a computer, the command multiple computers installed QTP run the script, would not cool zai.
Mercury developed Quanlity Center (referred QC), you can achieve this functionality.
To use QC remote call QTP, the need for a series of settings can be achieved. In this article, we deployed QTP's computer called "test machine", the remote control tester of computer called a "console" to facilitate the explanation.
After the test machine Bahrain QTP, but also to install a plug-in: TDPlugin. This plug-in installer in the following TDPlugin directory installation disk, reboot after installation.
The following settings are very important, are described in detail in QTP installation guide, I am here to explain some key points. Installation Guide file name is: QT_Install_Guide.pdf. The specific content of the "Modifying DCOM Permissions Manually to Enable Remote QuickTest Execution" in this chapter.
First to set permissions windows login user instruction guide assumes that the file is a test machine and the console have been joined to the domain, in fact, does not join the domain, too feasible, but setting a bit different. We talk about the situation here is not joined to a domain. For example, we log in windows console with ctrlUser the user, then it must also be increased in the same name and password is also a test machine in the same ctrlUser user and add this user to the system administrators group.
If the two machines are joined to a domain, the more easy to handle, such as user logon domain console is ctrlDomainUser, so long as the system administrator sets of test machines where the user can add, say, log on the console users with administrator privileges testing machine.
The next step is to set up a test machine firewall, mainly open 135 ports and add AQTRmtAgent.exe Agent to the firewall exceptions list.
Then set the DCOM permissions, there are more setup steps in the Installation Guide document which said more clearly, mainly to add some users and groups to the list of allowed access.
After setting up the DCOM, we open QTP, Run option in the paging, the "Allow other Mercury products to run tests and components" selected.
Well, now open a Test, and then connect QC and QTP, QC to save this Test above. Log in on the console QC, a new set of tests, the Test to just join the test set. Then in the "Host Manager" inside the ip add in the test machine. Back to the test set window of this Test Plan "hostname" is designated as IP test machine, well, now run the test suite and you're done.
Then QTP testing machine will automatically start, run this Test, after the end of the run, test results are automatically saved on the QC server, we can view the test results on any computer.

 

*********************************************************************

QC during installation is the most problematic database (SQL, Oracle) and Jboss server 
databases (SQL / Oracle), JBOSS, QC launch three are independent, successful start qc tray does not mean that the successful launch jboss, 
not plus qcbin try, can confirm whether jboss started successfully. 

SQL database, for example: 
· SQL can not start normal reasons: 
        1. SQL installation problems 
        2. Check your username and password do not match 
· JBOSS normal startup must meet the following conditions: 
        1. The user must be an administrator to install, and with a password (which is a necessary condition for the installation of jboss) 
        2. JDK JDK own installation manual and configure the environment variables 

operating system preparation: 
        1. my computer -> properties -> advanced -> performance settings -> data execution protection -> for essential Windows programs and services enable DEP (2003 default installation to change this) 
        2. ensure that the port numbers are available: 8080,8083,1088,1089,4444,1433 etc. 
        3. Create a user has super administrator privileges, then enter the domain server computer name 


preparation before installation: 
If jBOSS often failed to start due to the following reasons 
1. the user must be an administrator to install, and with a password, which is a necessary condition for the installation of jboss 
2. my computer -> properties -> advanced -> performance settings -> data execution protection -> for essential Windows programs and services that enable DEP (2003 default installation to change this)
3. Ensure the following ports are empty 8083,1088,1089,4444 
4. Create a user without super administrator privileges, the domain name will enter the full name of the server computer.

Reproduced in: https: //www.cnblogs.com/alterhu/archive/2012/02/13/2348647.html

Guess you like

Origin blog.csdn.net/weixin_33795093/article/details/94029363