ey team foundation server to hp alm use case(s) …€¦ · ey team foundation server to hp alm use...
TRANSCRIPT
EY Team Foundation Server to HP ALM use case(s) execution Guide
Table of Contents 1. Accessibility Parameter ......................................................................................................................................... 2
HP Credential .................................................................................................................................................... 2
OpsHub Accessibility ........................................................................................................................................ 2
OpsHub Service................................................................................................................................................. 2
OpsHub TFS/HP Proxy service .......................................................................................................................... 2
How to Start/Stop Service ................................................................................................................................ 3
Cloud VM Accessibility...................................................................................................................................... 3
2. Use cases ............................................................................................................................................................... 4
Use Case 1 ........................................................................................................................................................ 4
Use Case 2 ........................................................................................................................................................ 7
Use Case 3 ...................................................................................................................................................... 14
Use Case 4 ...................................................................................................................................................... 18
4. Points to Remember ........................................................................................................................................... 21
HP History ....................................................................................................................................................... 21
TFS History ...................................................................................................................................................... 21
Conflict Configuration ..................................................................................................................................... 21
Known Issues .................................................................................................................................................. 21
1. Accessibility Parameter
HP Credential
HP ALM can be access using below URL, you can us IE or HP 12 ALM Explorer (HP Client) on your machine.
URL: http://eysql2012sp2:8080/qcbin/
Users:
User name: standarduser , Password: inte1GREAT
User name: syncuser , Password: Opshub123
HP Site Admin User:
User name: admin
Password: eyadmin
HP Projects:
EYCOLLECTION/ Project_Waterfall_Standarduser
EYCOLLECTION/ Project2_waterfall_Standardusr
OpsHub Accessibility
URL: http://eysql2012sp2:8989/OpsHubWS/
User name/Password: admin/password
OpsHub Service
OpsHub windows service is registered with name OpsHub Server Service.
You can start or stop OpsHub Service from the window services. You can refer this.
OpsHub TFS/HP Proxy service
TFS:
Communicate /bridge between TFS API and OpsHub, OpsHub TFS window service registered
which run on port 9090
OpsHub TFS Window Service name is OpsHubTFSService.
Service URL: http://eysql2012sp2:9090/TFSService
You can start or stop OpsHub TFS Service using this. Test the web service by opening this URL in
browser http://<hostname>:<9090>/TFSService. E.g. http://eysql2012sp2:9090/TFSService
HP:
Bridge between HP API and OpsHub, OpsHub HP service deployed in IIS. OpsHub HP ALM/QC
service require for certain operation only.
HP ALM proxy URL is http://localhost/HPQCService.asmx
You can start or stop OpsHub HP ALM Service using this. Service run on the default port 80. Test
the web service by opening this URL in browser http://<hostname>:<port>/ HPQCService.asmx.
E.g. http://localhost/HPQCService.asmx
How to Start/Stop Service
Window Service
Open Command Prompt -> Execute services.msc command. This command will open window
services. Inside service window search for the particular service name and can start or stop
service from there.
Service deployed on IIS
HP ALM Service deployed on IIS. Make sure that IIS server is running. Refer following to check
whether IIS is running or not.
From window start -> Search for application IIS (Internet Information Services) ->Open IIS ->from
left most connection tab ->Click on EYSQL2012SP2 connection->Check current action from the
right most tab named as Action -> if IIS is not running then stop action is disabled. If so click on
start action to start it.
Cloud VM Accessibility
Remote Desktop Computer Name: DomainEY.cloudapp.net:62626
User name: EY.EDEV.COM\EYADMIN
Password: inte1GREAT
2. Use cases
We have consider four use cases for EY integration configuration.
Use Case 1 A requirement is created in TFS, it gets replicated to HP as requirement. Further if any update on
requirement is done in TFS, it should be replicated to HPALM and vice-versa. We will use multiple
project scenario for this use case.
Login in TFS -> Click on New ->Functional Requirement.
Fill up basic fields for requirement that we have mapped are Title, Description, priority (e.g. Low) as well
attachment (refer use case 1.2 figure).
Use Case 1.1 Figure
Once Functional requirement created go to HP (use IE or HP explorer)
From left most panel -> select the requirements tab->inside this tab you will find your synced Requirement from
TFS under requirements root folder (refer use case 1.4 figure).
Use Case 1.2 Figure
Use Case 1.3 Figure
Here under Requirements root folder you can see the TFS requirement synced. Requirement synced with basic
fields we have mapped along with attachment added in TFS.
Additionally associated TFS work item’s link stored in HP link to remote entity custom field.
Update this synced requirement in HP, update basic mapped fields like Name, Priority (High) and Description.
Use Case 1.4 Figure
Use Case 1.5 Figure
Go to TFS-> Check for updated requirement in TFS
Requirement updated in TFS with updated value from HP. Like Title, Description, Priority (High) etc.
Use Case 2 A Test Case is created in HP ALM and link it to the requirement created in use case one in HP under
Requirement Coverage, it gets replicated to TFS as Test Case along with the linkage.
Go to HP -> Select the Test plan tab from left most panel->Click on New Test Icon on top of menu icon(refer use
case 2.2 Figure)
Use Case 1.6 Figure
Use Case 2.1 Figure
Create Tests in HP with mapped basic fields like Test Name, Description, Status as well add an attachment to Test.
Use Case 2.2 Figure
Now add requirement coverage linkage to Test.
Go to Req Coverage tab for selected test -> Click on Select Req Option -> from requirement tree section click and
add above synced requirement
Now add steps to Test created in HP and go to Design Steps tab and click on New Steps icon
Use Case 2.3 Figure
Use Case 2.4 Figure
Provide steps details like description, execution result and attachment to that step and click ok to submit step.
You can see steps added under Design Steps
Use Case 2.5 Figure
Use Case 2.6 Figure
As soon as Test synced to TFS a link to TFS Test Case added in HP inside link to remote entity custom field.
You can see Test get synced to TFS as Test Case. Test case synced in TFS with basic fields mapped along with steps
Use Case 2.7 Figure
Linkage of Test case with Requirement also get synced in TFS, you can see that inside all link tab in TFS.
Test Case attachment also gets synced in TFS.
Update synced Test Case in TFS, update Title and add one more step.
Updates from TFS gets synced to HP Test. Check the design steps tab for newly synced step.
Use Case 2.8 Figure
Use Case 2.9 Figure
Use Case 3 Defect is created in HP and linked it to created Test Case in use case two. Defect will get replicated in
TFS along with linkage.
Go to Linked Defect tab of particular test (let say the test which we have synced previously)
Use Case 3.1 Figure
Create Defect in HP with basic fields like Summary, Description, Severity, Priority and Assigned to as well add an
attachment to defect.
As soon as Defect get synced in TFS, link to that TFS Bug added in HP link to remote entity custom field.
Use Case 3.2 Figure
Go to TFS UI -> you can see the synced Defect from HP to TFS with basic fields values. Defect created in TFS with
Title, Repro Steps, Severity, Priority etc. fields which we have mapped.
Defect’s attachment also gets synced. (Check the attachment tab)
Use Case 3.3 Figure
Even Defect’s linkage with Test case also get synced in TFS (Check the all links tab)
]
Now let update Defect in TFS. Update Title and Priority (High).
Use Case 3.4 Figure
Updates of Defect from TFS also get replicate in HP.
Use Case 4 Test cases, with requirements linked to them, are created in TFS (either manually or through eDev
SmartViso4TFS). These are replicated to HP.
Create new Test Case in TFS with basic fields like Title, State and Design Steps.
Use Case 4.1 Figure
Newly created Test Case in TFS will get sync to HP with basic fields + Design Steps along with requirement linkage.
Use Case 4.3 Figure
4. Points to Remember
HP History In HP if certain fields are updated like design steps or certain operation performed like add or delete
of link for such updates revision history is not generated due to which those update will get synced
when next time history get updated. For certain fields by default history is not enabled like
description for such fields even it is possible to enable history from HP ALM customize section. Even
though still there are some fields for which you cannot enable history like design steps.
TFS History Similar to HP, in TFS There are some operation for which revision are not generated like when we add
or delete link for any work item. For this history is added in history section but revision not updated
due which that link update will get sync either with previous or next revision sync.
Conflict Configuration For all the above four use cases we have configured conflict detection. We have considered TFS as
master system and in case of any change done in TFS will retain in HP. We have enabled conflict for
basic fields we have mapped. (Title, Description, Priority, State etc.)
Design Steps
We don’t support the design steps conflict detection as any change to this field will not make
a history due which we cannot detect conflict. So for above use case we have not enabled
conflict detection on design step.
Known Issues
HP Known Issue’s
1) In HP each requirement we create will created under the root requirement (default root folder
requirement in HP) named as requirements. HP provide only a read access to this root
requirement not a write access.
To have consistent hierarchy in both HP and TFS end we have synced this root requirement from
HP to TFS. As well sync the linkage of this requirement with all sub requirements whenever sub
requirement get synced first time in TFS.
Issue is if any update made to this root requirement in TFS once it gets synced to TFS like Title
change. Those updates will not synced back to HP.
2) In HP cross project linkage is not supported. For example requirement 1 of project 1 cannot be
linked to requirement 2 of project 2.
In TFS cross project linkage is supported as the other end point HP does not support. So any such
linkage done in TFS will not sync and result in failure.