Showing posts with label HP-QC Test lead Responsibilities. Show all posts
Showing posts with label HP-QC Test lead Responsibilities. Show all posts

Sunday, January 27, 2013

HP-QC (Test lead Responsibilities) Defining Testing Levels


Defining Testing Levels:

In defining testing levels, test lead can follow the below navigation:

QC Explorer---> Browse QC bin URL---> Click GO---> Enter user id and password by test lead---> Click Authenticate to get domain name and the corresponding project name---> Click login---> Click close in the welcome screen---> Management components---> Releases folder--->Releases menu---> New Releases Folder --->Enter project name as folder name---> Releases menu -->New Release---> Enter build version as release name---> Click OK---> Releases menu---> New cycle---> Enter testing level as cycle name(Follow above navigation to create cycles for all build versions)---> Do logout.

Example:Project name
                      |
               Version 1.0
                      |
              1) Smoke test
              2) Real test
                      |
               Version 1.0
                      |
              1) Smoke test
              2) Re test
              3) Sanity test
              4) Regression test
              5) Further real testing
                     .
                     .
                     .
                Version N.0
                      |
              1) Smoke test
              2) Re test
              3) Sanity test
              4) Regression test
              5) Final regression testing (Post mortum)




HP-QC (Test lead Responsibilities) Allocating Work As Testing Topics Wise:

After completion of work allocation modules wise to the testers, corresponding test lead can allocate work to the testers as testing topics wise.

Allocating Work As Testing Topics Wise:.

To give permission to the different roles, test lead can follow the below navigation:

QC Explorer---> Browse QC bin URL---> Click GO---> Enter user id and password by test lead---> Click Authenticate to get domain name and the corresponding project name---> Click login---> Click close in the welcome screen---> Test plan component---> Subject folder---> Enter testing topic as folder name---> OK (Follow above navigation to store all responsible testing topics names as folders)---> Logout.

Example: Subject
Functional testing                 ----- Pradeep
Usability testing                   ----- Srikanth
Compatibility testing            ----- Ramu
H/W configuration testing    ----- Vamshi
performence testing            ----- Geethika
Installation testing               ---- Pradeep





HP-QC (Test lead Responsibilities) Allocating Work To Testers

After completion of employees with assigning different roles and permission selections for each role, corresponding test lead can assign work to selected testers as TD admin.

Allocating Work To Testers (Module wise)

To give permission to the different roles, test lesd can follow the below navigation:

QC Explorer---> Browse QC bin URL---> Click GO---> Enter user id and password by test lead---> Click Authenticate to get domain name and the corresponding project name---> Click login---> Click close in the welcome screen---> Requirement components---> Requirement  folder--->Requirement menu---> New requirement --->Select requirement type as testing ---> Enter module name as requirement name---> Click OK---> Select responsible user name as Author---> Click Submit---> Close.

Follow above navigation to allocate all modules.

Example: Requirement Components
Login module      ----- Pradeep
Cheque Deposit ----- Srikanth
Money Transfer  ----- Ramu
Mini statement    ----- Vamshi
Bills pay               ----- Geethika
Logout                 ----- Pradeep

Like above wise all the modules in the project was assigned to the team members in the current project by the test lead.








HP-QC (Test lead Responsibilities) Permissions To Roles

After completion of employee selection for current project with different roles, corresponding test lead can give the permissions to those roles as TD admin.

Permissions To Roles:

To give permission to the different roles, test lesd can follow the below navigation:

QC Explorer---> Browse QC bin URL---> Click GO---> Enter user id and password by test lead---> Click Authenticate to get domain name and the corresponding project name---> Click login---> Click close in the welcome screen---> Tools menu---> Customize---> Module access---> Select and deselect different permissions to different roles---> Click return---> Do logout.
HP-QC (Test lead Responsibilities) Permissions To Roles






HP-QC (Test lead Responsibilities) Allocating Employees To Current Project

In general, test lead is working as administrator for testing related database in server.So, test lead can do more tasks in QC software.
HP-QC (Test lead Responsibilities) Allocating Employees To Current  Project
 Allocating Employees To Current  Project

For allocating employees to the current project, Test lead will follow the below navigation:

QC Explorer---> Browser QC bin URL---> Go---> Enter user name and password---> Click authenticate by test lead to get domain name and corresponding project name---> Click login---> Click close in welcome screen---> Tools menu---> Customize---> Project users---> Add users button---> Click OK to get list---> Select user name and provide role(PM,TD admin,QA tester,Developer, viewers)---> Follow above navigation to add different roles---> Click return---> Do logout.

Note: In general Test lead is only the person to working as TD admin to handle administrator tasks on database in server computer.





Recommend on Google

 

Followers

Popular Posts