Hp-QC Tutorial: Quality Center - Project Customization - SQA Geek

Quality is never an accident;
it is always the result of intelligent effort.

Post Top Ad

Friday 13 November 2015

Hp-QC Tutorial: Quality Center - Project Customization

Project Customization

Sometimes we are in a situation to customize the project. Below are the modules which will help us in customizing the project. Click on each one of these links to understand the functionalities in detail. Project Customization module can be accessed by navigating to "tools" >> "Customize" as shown below:
Customization 1
When a project administrator accesses project Customization then following modules would be shown to the user for custmization.
Customization 2
FunctionalityDescription
User PropertiesHelps user to update profile details.
Project UsersAdd/Remove user and user roles.
Groups and PermissionsAdd/Remove group previleges.
Module AccessEdit Module Level Access.
Project EntitiesAdd/Edit/Delete Project Fields
Requirement TypeCreate,Edit,delete requirement Type
Project ListsAdd,Edit,Delete all project list box fields.
AutomailSend mail based on specific settings.
Alert RulesAlert users based on specific changes.
WorkFlowDefect Fields Customization.

User Properties

User properties module helps users to customize their user profile information such as name, email ID and also helps users to change password.
Click "User Properties" Link which is on the left pane of the project customization window.
qc user properties 1
Click "Change Password" button on user properties pane. Current logged in users credentials can only be changed.
qc user properties 2
Users can also update their personal profile information and hit save.
qc user properties 2

Project Users

This module helps us to add a list of valid users from the overall ALM users list. In addition to that we can also assign each project user to a user group. Each user group has a specific permissions to perform certain tasks.
Click on "Add user" button which in project users module.
qc project users 1
The "Add user" dialog opens. The project administrator has to key in the user name inorder to add users successfully.
qc project users 2
After adding the user successfully, Select the user to whom the membership levels has to be edited. Select the Membership level and click on ">>" button.
qc project users 3
Project Administrators can also remove an user from the project area using "Remove user" button. Remember this will just remove the user from the project areas and it will still retain the user in HP-ALM site Administration.
qc project users 4

Groups and Permissions

To protect a project from unauthorized access, ALM enables project administrators to assign each user to one or more predefined with default privileges that has access to perform certain ALM actions.
Select "Groups and Permissions" Link and user will notice that there are five user groups by default. The below groups and permissions are known as System groups and are "READ ONLY". The Permissions of those CANNOT be modified(Edit/Remove) even by project administrators.
  • Developer
  • Project Manager
  • TD Admin
  • QA Tester
  • Viewer
Each one of those user groups displays membership information which shows the users "In group" and "Not in group".
qc project users 1
The Next tab "Permissions" shows the permission levels for the selected "Group". It is READ ONLY and Cannot be edited for the above said default groups. It shows that the group "QA Tester" has permissions to create and update defects but can't delete.
qc project users 2
In case user wants to create a customized user group, they can do so by hitting "New Group" button and select the name of the group and type of profile they would like to create.
qc project users 2
In the below scenario, we allow "Business Analysts" user group to create and update requirement but cannot move/delete. We can customize each one of the areas such as tests, defects according to our requirements.
qc project users 2


Module Access

Module Access allows project Administrators to control the level of access for each one of those user groups that we discussed in groups and permissions module. By Default all types of users have access to all modules however they are NOT allowed to perform all actions which are controlled in permissions module.
qc project users 2
As per below snapshot, user can turn off Test plan module for user group "Business Analyst". Similarly components and models module are turned off for all user groups.
qc project users 2


Project Entities

Some times project administrators would be in a position to customize a project to meet the specific needs of project. Hence we might have to add or customize fields, customize requirement types, and create categories and lists to meet the needs of the project. We should also keep in mind that the System fields are default fields and cannot be added or deleted but can be modified. This module deals with how to create/edit customize fields.
Let us understand this topic with an example. We will add a user defined field "Build Number" as a text box in "New defects" Module.
Step 1 : Goto Project Entities and select "Defect". Hit "New Field" Button after selecting the "User Fields" folder.
qc project users 2
Step 2 : Enter appropriate label name and select the correct data type "String/Date/User List/lookup List/Number/Float". We can also make it as "Required" Field so that user has to enter that field inorder to successfully post a defect. After creating the user defined field hit "Save".
qc project users 2
Step 3 : Click "New Defect" Button in defects module. The user defined field will pop up and it will be shown as the mandatory field as we have marked it as a "Required" field while creating the same.
qc project users 3
Step 4 : Similarly we can create user defined fields across modules whereever necessary. Please do note that for creating a user defined Look up list one has to create the list using project lists and the select the list while creating a user defined field.


Requirement Types

This module helps us to create different requirement types apart from the default ones and also allows us to customize their properties. These requirement types are shown as a list to the user in "Create Requirements" page.
qc req types
Project Administrators can create a New requirement type and map it against a predefined requirement type. Each requirement type has got System Fields and User defined fields associated with it.
qc req types 2
Project Admins can also "Rename" or "Delete" a predefined or user defined requirement type.
qc req types 3
Afer creating a new requirement type, the user can choose the created requirement type("look and feel" in this case) while creating new requirements.
qc req types 3


Project Lists

Project Lists module allows user to create, rename, and delete user-defined lists. All the prepopulated drop downs are known as system lists while user can also create their own list. The default System list is shown below.
qc req types
Project Admins can create a user defined list(say language list) and add items to the list.
qc req types 2
While adding items to the user defined fields, user can add it as a main item or a sub item. They also have access to rename/delete the user defined lists.
qc req types 3
System defined lists Cannot be delete or renamed, however new items/sub items can be added to the list.
qc req types 3


Automail

ALM enables the users to automatically notify them via email each time a specific defect fields changes. Configuring mail for an ALM project involves the below steps:
Click the link "Automail" Link in "Project Customization" page.
qc req types
Project Admin can select, under what circumstances mail should be triggered. Project Admin can also select as many fields as they can and select "To" users. Users can also filter the criteria the project users to receive an email.
qc req types 3


Alert Rules

When an entity changes(requirement, defect, test runs), project admins can instruct ALM to notify those responsible for any associated entities that may impact the application management process. The below setting shows that the default alert rules.
qc req types
The below setting will alert the both the entity as well as the person responsible for it.
qc req types 3


Workflow

The Workflow module provides links to script generators and a script editor. Script generators are used to perform customizations on the input fields of the Defects module dialog boxes while the script editor is used to create scripts to control the workflow in any ALM module.
qc req types

Script Generator - List Customization

When workflow customization is used to change a list of values for a field that has transition rules defined, the field may only be modified in a way that satisfies both the workflow script and the transition rules.
Select Primary field and when it changes, user can set an appropriate secondary field. In the below example, we have selected the primary field as target cycle and priority as secondary field.
qc req types 3
Upon setting the primary and secondary field, click "Apply Script Changes". Upon clicking "Apply and View", the script window will be opened with the script placed in appropriate place.
qc req types 3

Script Generator - Add Defect Field Customization

This module helps project admins to configure the fields that should be displayed in "new defect" dialog for each one of the user profiles. First Select the user profile and by default all the fields are visible to the Admin user in "New Defect" dialog. But, user can push the fields out of visible fields and also make any field mandatory by checking the field "ON" under visible fields pane.
qc req types 3
Click on "Apply and View" , the Script editor window opens and shows the changes as script. Scroll down and check "TD Admin" profile which we have modified just now. Following things are to be noted.
  • The First Parameter corresponds to the Field Name
  • The Second parameter corresponds to the "Visiblity" flag. If Set "True" then it is visible.
  • The Third Parameter corresponds to the "Mandatory" Flag. If set "True" then it is Mandatory.
  • The fourth parameter corresponds to the Page Number. If "0" then it will display in the first page.
  • The last parameter corresponds to the view order. The field with flag 0 will be displyed first and field with flag value "1" will be displayed next and so on.
qc req types 3
Now let us take a preview of the "TD Admin" user group's "Add Defect" Window.
qc req types 3

Script Generator - Defect Details Field Customization

This module helps project admins to configure the fields that should be displayed in "View defect Details" dialog for each one of the user profiles. First Select the user profile and by default all the fields are visible to the Admin user in "View Defects Defect" dialog. But, user can push the fields out of visible fields and also make any field mandatory by checking the field "ON" under visible fields pane. It works the same way as that of "Add Defect Field" Customization.
qc req types 3
Click on "Apply and View" , the Script editor window opens and shows the changes as script. Scroll down and check "TD Admin" profile which we have modified just now. Following things are to be noted.
  • The First Parameter corresponds to the Field Name
  • The Second parameter corresponds to the "Visiblity" flag. If Set "True" then it is visible.
  • The Third Parameter corresponds to the "Mandatory" Flag. If set "True" then it is Mandatory.
  • The fourth parameter corresponds to the Page Number. If "0" then it will display in the first page.
  • The last parameter corresponds to the view order. The field with flag 0 will be displyed first and field with flag value "1" will be displayed next and so on.
qc req types 3
Now let us take a preview of the "TD Admin" user group's "View Defect details" Window.
qc req types 3

Script Editor

Script Editor helps the project Admins to create a user-defined workflow script. From the below screenshot it is obvious that a script can be created commonly across modules or specific to a module viz - test lab, defects etc.
qc req types 3

No comments:

Post a Comment

Post Bottom Ad