How to use QC to manage testing

No 1: As a QA leader, if you need QC to manage testing work, you can do as the following:

(1)  Creating project in QC Site Administration

(2)  Setting up groups in QC Tool Customization

(3)  Adding users to group

(4)  Adding fields in QC

(5)  Importing Requirements

(6)  Maintaining clarification logo

No 2: QTP object repository usually likes the following:

(1)  There are two kinds of object repository: local and share

(2)  Object repository framework: common object repository, common script, common parameter

(3)  Object repository Library: Pro object repository, Pro test script, Pro test parameter

No 3: If you have built connection between QTP and QC, however, QTP script. cann’t run in QC, you can do as the following:
(1) In QTP, clicking “Tools”--->”Options”--->”run”

(2) In “run” page, checking on “Allow other Mercury products to tests and components”

(3) In QC, run QTP scripts again

No 4: Create project template in QC Site Administration

(1) In browse address, input “http://XXX.XXX.XXX.XXX:8080/qcbin/”

(2) Clicking “Site Administration”, and open “Site Administration” page

(3) Selecting one domain

(4) Clicking “Create Project”, then you can set fields and save it as project template

No 5: Identify testing process by QC; you can identify some fields if you need.

(1)  Requirement, before import requirements, we need to add these fields:

1’out of scope---value (review status)

2’application screen---field (parent/group name, filter nonrequirements)

3’change priority---value, opposite to defect’s priority (1-urgent....5-low)

4’review comment

5’Release

(2)  Test Plan, before making test plan, we need to add these fields:

1’peer review

2’Developer review

3’sign off

4’assigned

5’reviewer

6’comments

7’version

8’automatic---Y/N

9’Application Screen

10’priority

(3)  Test lab, before executing test case, we need to add these fields:

1’environment---field, it contains these values: test, stage, development, production

2’Instance

(4)  Defect, if we need, we can add these fields:

1’reviewer

2’enhancement---Y/N

3’assigned by

4’group, it contains: Developer, tester, user

No 6: Who manage requirements?

(1)  BA manage requirements

(2)  QA can review it

(3)  QA cann’t remove requirement

No 7: How to distribute permission to each group?

(1)  tools--->customization--->set up groups

(2)  choose one group, click “view” button

(3)  click “defect”, select “status”, you can change the transition rules of status

No 8: How to create test lab?

(1)  Create test set

(2)  Click “Select Tests” and select “test case”

(3)  Click “Add tests to test set”

No 9: How to create test plan tree?

(1)  Usually, we set up these groups in test plan: release, regression, automated, removed

(2)  We use control no(010...) to identify different level

(3)  We can do as the following figure: