QTP is licensed as either seat or concurrent license. A seat license is tied to a physical machine and can only be used on that machine. Eg License1 for machine1, license2 for machine2 and so on.
Concurrent license on the other hand is installed on a server and depending on the licenses we buy, any computer on the network can run QTP. Eg. If we have 4 concurrent licenses, at any given time 4 machines can run QTP. QTP can be installed on all machines/ selected machines on the network, but at any given time 4 machines can run qtp.
Concurrent licenses are more popular esp when there are global teams, the licenses can be used in different timezones to get maximum ROI from automation. Also since the license is not tied to a machine, but tied to the server, there is more flexibility in usage. Resources who are telecommuting can also use the commuter license when they are travelling if they cannot connect to the concurrent license server.
Previously, QTP was licensed separately, but in recent times, HP has packaged QTP and Service Test into a bundle called HP Functional Test. The procedure for installing the license is the same as before. You need not install QTP and Service Test concurrent licenses separately. The only thing you need to install is the HP Functional Test concurrent license and you can use both QTP and HP service Test. Also all add-ins are available as part of the package. No separate licenses for add-ins.
Prerequisites:
1. A windows 2003 server (machines with other OS can also be used as the server. Check the installation guide)
2. QTP concurrent license e-Software Delivery Confirmation
3. A client machine (to install QTP). Note: QTP can also be installed on the windows 2003 server on which the concurrent license is installed. But in real time testing teams, QTP will be installed on multiple machines which talk to the concurrent license server for license validation.
Steps:
1. Connect to the client machine. Ping the server. You need to ensure that there is connectivity between the client and the license server.
2. There will be a link to the software in the e-software delivery confirmation. Register and login to the site, if you have not done so before.
3. If you click on the get software tab, download the HP UFT 11.00 CC Eng SW E-Media, Software, QTP 11.00 English ( T6510-15066.iso )
Basically, it is the QTP installer.
4. Copy the installer to the windows 2003 server machine. Click on the Install concurrent license server link, HP uses the Sentinel LM license server which will be installed, just follow the instructions on screen.
5. Next, you need to install concurrent license. Click on the install concurrent license link. When you do so, a locking code will be displayed when you follow the on screen instructions.
5. Now, copy the locking code. Click the link for the software e-delivery confirmation again and click on the get licensing tab. When you click get licensing, it will ask for the locking code. Enter the code in the box, and it also will ask you how many licenses you want to activate. You can enter the number of licenses you purchased, once you confirm your details (as the license owner) and enter the email ids to which you want the license code to be sent, you will get the license key displayed on screen. (a string of characters). It will also be emailed to you. Also print the license entitlement certificate and save it for records.
6. Login to the server again and click on install concurrent license key, and you will find a box to enter the license key. Copy paste the code to the box and press confirm. The concurrent license is installed. You will get a message saying that the concurrent license is installed and you need to restart the server.
7. Now, download HP service Test installer and copy it to the client machine. Also copy the QTP installer to the client machine. Install both service test and qtp on the client machine.
8. When you start QTP and service test, it will ask for the license type, select concurrent and enter the ip or the machine name of the server machine. If the server and client are on the same subnet, then you will have no issues.
9. If QTP does nt start up, on the client machine, go to computer--> properties--> environmental variables --> system variables and add variable LSHOST and give the value as the concurrent server name or ip. Now, try opening QTP again, you should be able to connect to the license server.
and you're done!!
The user guide for installing HP functional test is quite comprehensive and has step by step instructions. It is available along with the software. You can find it under the help menu in QTP.
Monday, August 8, 2011
Wednesday, June 29, 2011
Adding a project user group as valid users
The list of Valid users only contains global groups as shown below.
If you want to add project groups as valid users, the values are not shown in the drop down. Entering the value [Project1]\Usergroup throws the error
TF26204: The account you entered is not recognized. Contact your Team Foundation Server administrator to add your account.
If your project name is helloworld and usergroup name is testing, enter [project]\testing and save. Do not replace [project] with your project name.
View XML shows the following value after saving.
If you want to add project groups as valid users, the values are not shown in the drop down. Entering the value [Project1]\Usergroup throws the error
TF26204: The account you entered is not recognized. Contact your Team Foundation Server administrator to add your account.
If your project name is helloworld and usergroup name is testing, enter [project]\testing and save. Do not replace [project] with your project name.
View XML shows the following value after saving.
Making "Found In Build" a mandatory field
1. Open the Bug work item definition from Process Editor.
2. Select the "Workflow" tab
3. Double click the "New" state to open the "Work Flow State Field Rules" window
4. Click "New" and select "Microsoft.VSTS.Build.FoundIn"
4. Click "Rules" and select "Required". Save the work item definition.
5. Now "Found in Build" is added in the state diagram.
6. Once this is done, when creating a new defect, the user cannot save without entering the "found in build"
2. Select the "Workflow" tab
3. Double click the "New" state to open the "Work Flow State Field Rules" window
4. Click "New" and select "Microsoft.VSTS.Build.FoundIn"
4. Click "Rules" and select "Required". Save the work item definition.
5. Now "Found in Build" is added in the state diagram.
6. Once this is done, when creating a new defect, the user cannot save without entering the "found in build"
TFS Defect Workflow Customisation - Adding Values for "Found In Build" as a predefined list when build is not generated from TFS
1. From the process editor, open the work item definition for "Bug"
2. Click on the "Fields" tab and double click "Found In"
2. Click on the "Rules" tab --> "New" and add the value "Allowed Values"
3. Click on the "Allowed Values" tab --> "New" and add the value wanted in ur listbox like "1.0". Repeat to add new values and "save" the work item definition.
Now, when creating a new bug, the values added here, will be autopopulated as a list in the bug.
2. Click on the "Fields" tab and double click "Found In"
2. Click on the "Rules" tab --> "New" and add the value "Allowed Values"
3. Click on the "Allowed Values" tab --> "New" and add the value wanted in ur listbox like "1.0". Repeat to add new values and "save" the work item definition.
Now, when creating a new bug, the values added here, will be autopopulated as a list in the bug.
Tuesday, June 7, 2011
Defect Workflow customisation in TFS
Download and install team foundation server 2010 power tools. The process editor has a user interface using which you can do the workflow customisation.
Open VS2010, connect to the tfs server. You will see the Process editor under Tools Menu.
Go to Tools-->Process Editor--> Work Item Types-->Open WIT from Server.
Select the workitem type "Bug" to edit from the project for which you want to set up the defect workflow.
Go to the workflow tab, there is a diagrammatic representation of the defect workflow provided by default. This can be edited.
The defect workflow consists of
a) State denoted by a red box
b) transition denoted by the transition rules box and connectors
You can use the toolbox to add the states and transitions, by dragging and dropping them onto the workflow pane.
When you right click on a state, you can add/edit an existing Ref Name
Add a new Ref Name/ Click on an existing one to set rules.
We can edit the workflow transition, by double clicking on the transition box.
The default reason and additional reasons can be specified.
Actions can be added as well.
Field references can be added.
Open VS2010, connect to the tfs server. You will see the Process editor under Tools Menu.
Go to Tools-->Process Editor--> Work Item Types-->Open WIT from Server.
Select the workitem type "Bug" to edit from the project for which you want to set up the defect workflow.
Go to the workflow tab, there is a diagrammatic representation of the defect workflow provided by default. This can be edited.
The defect workflow consists of
a) State denoted by a red box
b) transition denoted by the transition rules box and connectors
You can use the toolbox to add the states and transitions, by dragging and dropping them onto the workflow pane.
When you right click on a state, you can add/edit an existing Ref Name
Add a new Ref Name/ Click on an existing one to set rules.
We can edit the workflow transition, by double clicking on the transition box.
The default reason and additional reasons can be specified.
Actions can be added as well.
Field references can be added.
Silverlight Application Deployment - Part 5
From the previous post, these are the major steps.
1. Install prerequisites for deploying through TFS
2. Deploy the silverlight application
3. Configuring IIS
4. Database configuration
In this post, We'll cover
4. Database configuration
Once you install SQL Server 2008.
1. Ensure that you are logged in as the sa before you create database
2. Login as sa and Create the user NT AUTHORITY\NETWORK SERVICE in SQL Management Server -->Security-->Logins. Right Click and create a login "NT AUTHORITY\NETWORK SERVICE"
1. Install prerequisites for deploying through TFS
2. Deploy the silverlight application
3. Configuring IIS
4. Database configuration
In this post, We'll cover
4. Database configuration
Once you install SQL Server 2008.
1. Ensure that you are logged in as the sa before you create database
2. Login as sa and Create the user NT AUTHORITY\NETWORK SERVICE in SQL Management Server -->Security-->Logins. Right Click and create a login "NT AUTHORITY\NETWORK SERVICE"
Silverlight Application Deployment - Part 4
From the previous post, these are the major steps.
1. Install prerequisites for deploying through TFS
2. Deploy the silverlight application
3. Configuring IIS
4. Database configuration
In this post, We'll cover
3. Configuring IIS
This consists of the following
a. Adding Mime Types
b. WCF and Dot net framework installation
a. Adding Mime Types
Go to Control Panel--> Administrative Tools --> IIS Manager
Right Click on the virtual directory created earlier --> Properties --> Mime Types --> New
Add the following Extensions and Mime Types, one at a time.
• .xap application/x-silverlight-app
• .xaml application/xaml+xml
• .xbap application/x-ms-xbap
Click ‘Apply’
b. WCF and Dot net framework installation
1. Install prerequisites for deploying through TFS
2. Deploy the silverlight application
3. Configuring IIS
4. Database configuration
In this post, We'll cover
3. Configuring IIS
This consists of the following
a. Adding Mime Types
b. WCF and Dot net framework installation
a. Adding Mime Types
Go to Control Panel--> Administrative Tools --> IIS Manager
Right Click on the virtual directory created earlier --> Properties --> Mime Types --> New
Add the following Extensions and Mime Types, one at a time.
• .xap application/x-silverlight-app
• .xaml application/xaml+xml
• .xbap application/x-ms-xbap
Click ‘Apply’
b. WCF and Dot net framework installation
Subscribe to:
Posts (Atom)