Embed Size (px)
Citation preview
1
Quality Center 9 - Customizing
Presented by:Knud AndersenSenior Architect
Presented to:HPTest user group
2
Agenda
Organization wide Customizing
Project Specific Customizing
Workflow Customizing
Scripting
Questions
3
Organization wide Customizing
Customization done in Site Administration (settings tab)
SHOW_REPOSITORY_OVER_DBAllow projects to store repository data in databaseSELECT_FS_OVER_DBShow repository data in database as default selectedWAIT_BEFORE_DISCONNECTTimeoutADD_NEW_USERS_FROM_PROJECTAllow new users to be added from project administrationSITE_ANALYSISShow Site Analysis tab in Site AdministrationBAKCWARD_SUPPORT_ALL_DOMAIN_PROJECTSAllow programs using QC API to connect using ‘old’ method
4
Organization wide Customizing
5
Organization wide Customizing
6
Project Specific Customization
7
Project Specific Customization
Requirement CustomizationFrom QC 9.2 – New Requirement types
• Create new requirement types• Customize existing requirement types
From QC 9.2 – Risk Based Testing• Risk Based Quality Management
– Business Criticality» Built in + define your own rules
– Failure propability» Built in + define your own rules
8
Project Specific Customization
9
Project Specific Customization
Requirement CustomizationFrom QC 9.2 – New Requirement types
• Create new requirement types• Customize existing requirement types
From QC 9.2 – Risk Based Testing• Risk Based Quality Management
– Business Criticality» Built in + define your own rules
– Failure propability» Built in + define your own rules
10
Project Specific Customization
11
Project Specific Customization
12
Project Specific Customization
13
Project Specific Customization
Customization done in Projects (Site Administration)Renaming Modules
E.g. Bug instead of DefectProject Table, DATACONST
• Insert value: REPLACE_TITLE
INSERT INTO DATACONST (DC_CONST_NAME) VALUES ('REPLACE_TITLE')
Update DATACONST set DC_VALUE = 'Defect;Bug;Defects;Bugs' WHERE DC_CONST_NAME = 'REPLACE_TITLE‘
UPDATE DATACONST SET DC_VALUE='original title [singular]; new title [singular]; original title [plural]; new title [plural]' WHERE TABLE_NAME='REPLACE_TITLE’
Transition RulesUser groups
• Can do …
14
Project Specific Customization
15
Project Specific Customization
Transition RulesCustomizing Users
• User Group– Permissions– Defect Values
» Transition Rules – can only change from - to
Defects data hidingFilter to hide dataVisible / hidden fields
• based on user group (access level)
16
Project Specific Customization
17
Project Specific Customization
Transition RulesCustomizing Users
• User Group– Permissions– Defect Values
» Transition Rules – can only change from - to
Defects data hidingFilter to hide dataVisible / hidden fields
• based on user group (access level)
18
Project Specific Customization
19
Project Specific Customization
20
Project Specific Customization
21
Project Specific Customization
Customizing Alert RulesCustomizing Module Access
Project EntitiesCannot delete:
• Y, N From Yes/No list• New, Open, Fixed, Closed From Bug Status list• No Run, Passed, Failed From Status list
22
Project Specific Customization
23
Project Specific Customization
24
Project Specific Customization
Customizing Alert RulesCustomizing Module Access
Project EntitiesCannot delete:
• Y, N From Yes/No list• New, Open, Fixed, Closed From Bug Status list• No Run, Passed, Failed From Status list
25
Project Specific Customization
26
Project Specific Customization
Customization done in Projects (Customization menu)
Project EntitiesFields (System + User Defined)Lists (System + User Defined)
User GroupsPermissionsUsersMailTraceability
Workflow
27
Project Specific Customization
28
Project Specific Customization
Project EntitiesField Names
• Lookup ValuesLists
• Can have multi values selected from listsField Rules
– Label– History– Required– Verify
Field• Number / String / Date / User List / Lookup List
Memo Field
(Max 99 Fields – Max 5 Memo Fields)
29
Project Specific Customization
30
Project Specific Customization
31
Project Workflow Customization
Script GeneratorList CustomizationAdd defect fieldDefect details
List customization• E.g. Field Region
– If North» Subfield Area to show list of North Areas
– If South» Subfield Area to show list of South Areas
Defect Field Customization• Defect Add• Defect Details
32
Project Workflow Customization
33
Project Workflow Customization
34
Project Workflow Customization
35
Project Workflow Customization
36
Project Workflow Script
Customization done in Script (VBScript language)
WorkflowCommonRequirementsTest PlanTest LabManual RunnerDefects
<Entity>_<Event>Defects_Bug_New –> when adding a new defect, Bug_New is triggeredTest_Test_CanDelete -> when a testplan is deleted, Test_CanDelete is triggered
37
Project Workflow ScriptAdd a new button … execute Action Name
(Requirements_Action1)
38
Project Workflow Script
Function ActionCanExecute(ActionName)'Use ActiveModule and ActiveDialogName to get the current context.' For example:if ActiveModule = "Requirements" then
if ActionName="Requirements_Action1" thenmsgbox "Action in Requirements module"
end ifend ifActionCanExecute = True
End Function
39
Project Workflow Script
40
Project Workflow Script
..............If Fields("BG_STATUS").Value = "Closed" then
If ((Fields("BG_USER_04").Value = "") or (Fields("BG_USER_04").IsNull)) thenMsgBox "Field " & Bug_Fields("BG_USER_04").FieldLabel & _
" cannot be empty“Bug_CanPost = False
end ifend if
……........
If Status_IsChanged And Not RDComments_IsChanged ThenMsgBox "You must provide the explanation in <R&D Comments> " & _
“when defect <Status> is changed to '" & _Fields("BG_STATUS").Value & "'"
Bug_CanPost = FalseEnd If
41
Project Workflow Script
