QC 9.

2

Prepared By

Sriraman K

Objectives
‡ Test Management Tool ² What, Why, Benefits etc ‡ To make participants aware of Test Process and controlling the process through security.

2

Test Management Tool
‡ ‡ ‡ ‡ Test Management Overview What is Test Management Tool? Why Test Management Tool to be used? What are the benefits and false notion of using Test Management Tool? ‡ Various Test Management Tool tool in the market ‡ Introduction to QC ‡ QC course Content

3

Test Management Overview
Definition ‡ ´Manage and measure the application delivery process from a quality perspectiveµ Process
‡ Validate application functions against the functional specification, i.e., functions yield the expected results? ‡ Report and track defects ‡ Measure test coverage and track application quality

4

‡ Use of Test Management Tool tools reduces the reporting time as well as the cost. Test Scenarios.What is Test Management Tool ‡ Test Management Tool is a repository. Test Cases and Defects. ‡ It is meant for storing Requirements. 5 .

‡ The tool captures all the information entered by the users and gives the report to the management instantaneously. ‡ Sends mail or trigger an alert based on the type of data captured by the end user. ‡ Customizable to the need of the organization ‡ Process compliance 6 .Why Test Management Tool ‡ Avoid the errors that human make when they compile reports received from various people.

Benefits of Test Management Tool ‡ More consistent ‡ Reliable in compilation of reports ‡ All the reports are instantaneous and hence the status of delivery is clearly visible to management. ‡ Security ‡ Traceability Matrix ‡ Managing Change Request 7 .

Caution ‡ Needs discipline in entry otherwise the report will go havoc. ‡ The tool maintains history and hence one cannot cook-up data ² hence more compliance is required 8 .

What are the different tools available in the market (for functional testing) ‡ ‡ ‡ ‡ ‡ Rational Clear Quest Rational Test Manager Silk Central HP Quality Center Open Source Tools ² Bugzila. 9 . Jira etc.

Introduction to QC ‡ Developed by Mercury interactive Owned by HP presently ‡ QC is web based application. ‡ Customization Script developed on VB Script ‡ QC can be installed on Windows. Database as MS SQL or Oracle. server being IIS or Jboss. Linux and Solaris 10 . ‡ QC is formally known as Test Director.

Add Ins of QC ‡ For integrating with automation tool like QTP. QC requires Add in ± By Default QC supports ‡ Winrunner ‡ LR ± Other Addin ‡ QTP 11 . Winrunner.

Course Objective ‡ Site Administrator ± ± ± ± Managing Domain Managing Projects Managing Users Making user as Administrator to the project ± Site Connections ± License ± Site Analysis ‡ Quality Center ± Release & cycle ± Requirements ‡ Managing Requirement ‡ Customizing Requirements ‡ Reports ‡ Quality Center ± Customization ‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡ ‡ Users Groups Module Access Project Entities Project Lists Requirement Type Risk Based Quality Management Auto Mail Traceability Alert ± Test Plan ± Test Lab ± Defects ‡ Export From XLS ‡ Export From Word 12 .

‡ Create Domain ‡ Rename Domain ‡ Manage Projects ± Projects are the specific project by itself. test case and defects needs to be maintained. ± Each project is an database by itself ± Cannot link one project to another project 13 . of projects.Site Administrator ‡ Manage Domain ² ± Domain is a folder which can handle any no. whose Requirement.

Projects ² Contd. ‡ Manage Project ± ± ± ± ± ± Creation of Project Renaming a Project Pinging a Project Coping a Project Managing users to the project Making an user as Administrative user for a project ‡ Manage Users ± Creation of Users ± Association of users to the projects 14 .

Quality Center ‡ Customization ± Project Users ‡ Assigning users to the project ‡ Creation of new user to the project ‡ Mapping groups to the users ± Project Groups (what is groups and its importance) ‡ Creation of Groups ‡ Assigning users to the groups ‡ Customizing control using groups ± Field level control ± Setting the permission to change the data by created user and other user 15 .

Customization contd. ‡ Module Access ± Controlling license using Module access ± Need of Module Access ‡ Project Entities ² Works with Database Tables ± System Defined Fields ‡ Change Logical name for existing fields ‡ To configure history. Mandatory and searchable criteria to a field ± User defined fields ‡ As String ‡ As Date ‡ As Number ‡ As Blob ‡ As List and User List 16 .

Number ‡ Formatting the field (Masking) 17 . List. Blob. UserList.Customization Contd. ‡ Project Entities ± ± ± ± ± How to make a field as mandatory (Required) How to make a history to a field How to give formatting to a field How to include the field for search Creation of User defined field ‡ Mapping the field as String.

Customization ² Project Lists ‡ Project List ± Creation of New List and configuring the list using project entities ± Managing the existing list with new values ± Importance of checking the check box as Verify value of the project list in project Entities ± Controlling the work flow for a list box contents using Groups ± Effect of those in Requirements. Test Plan and Defects 18 .

Requirements ‡ Requirements ± Creating a Requirement ± Creating a sub requirement ± Testing the changed workflow in the project groups in requirements ± Testing the Mandatory. history setting at project groups ± Customizing the columns ± Different views of Requirements ‡ Coverage view ‡ Grid view etc. 19 .

Test Plan ‡ Test Plan ± Creation of Test Scenarios (Folders). ± Customizing user defined field and its effect under test plan ± Test Plan Details ± Different View for Test Plan ± Mapping Test cases to the requirement ± Reports ² Summary. Sub Folders ± Creation of Test Cases under Folders ± Checking the effect of permission by changing the setting in groups for various users. Progress. Trend 20 .

Test Lab ‡ Test Lab ± ± ± ± ± Creation of Rounds (Folder) Creation of Test Set Mapping test case to the test set Execution of Round Finding the actual result in the requirement after mapping ± Creation of defect while executing through execution screen ± Different execution reports 21 .

Through test lab 22 . Test case.Defects ‡ Defects ± ± ± ± Creation of Defects Managing the defect cycle by configuring through groups Effectiveness of security features of the defect status change Customizing defect for various groups ‡ Customizing the add defect screen ‡ Customizing the modify defect screen ± Various defect reports ‡ Defect aging ± Linking defects ² Requirements.

Steps include ± Block the content which needs to be imported in xls sheet 23 . Test Cases and Defects can be imported from XLS Sheet.Export From XLS file ‡ All Requirements.

Export From XLS Contd. ± Select Export to XLS from Tools and Connect to QC using valid user name and password as shown below 24 .

± Enter User Name and Password and select the domain and project from the list for that user. 25 .Export From XLS Contd.

± Select the Module to which the import to take place (Requirements or Tests or Defects) ± Select Temporary Map file (if you want edit latter you can save the file with map name) 26 .Export From XLS Contd.

± Select the fields from the list and use ³>´ and map to Excel column name 27 .Export From XLS Contd.

± Same way we can do for defects or Test Case 28 .Export From XLS Contd. ± Click on finish ± Go to QC and we can see the Requirements got added.

Export From Word ‡ Install the Word Add in provided by the QC ‡ Open the word doc file ‡ Tool bar has got added to the word open document ‡ Under Tools. Quality Center Link has got introduced. 29 .

± Enter the Requirement Name and Press Enter ± Click Description ± Enter Description and press Enter ± Click Review ± Enter Review value (as in the list box) (same way for author. Icon.Export From Word Contd. priority) ± Enter Author (as in the list box) ± Enter priority (as in the list box) ± Click Close Requirement 30 . ‡ Requirement Adding ± Click Open req.

‡ After the entry the word document will look as shown. ‡ For every requirement we need to close the requirement. ‡ For non selected Field it will take the default value 31 .Export From Word Contd.

Export From Word Contd. ‡ In the same way we need to do for Test case and it will look as shown ± ± ± ± ± ± ± ± Test Folder Test Case Name Designer Test Case Description Test Step Test Step Description Expected Result Close the folder at the end 32 .

Click on Export To QC icon ‡ Select the Server ‡ Enter UserName and Pass word 33 . ‡ Once done.Export From Word Contd.

Export From Word Contd. ‡ Select the domain and Project for which import has to happen ‡ Select Next and finish 34 .

Export From Word Contd. ‡ Go to QC ‡ Login and you can see the requirement added 35 .

36 . you can see that test folder and test cases with test steps got added.Export From Word Contd. ‡ In the test plan module.

± Product release and version control gets affected by customizing to individual customers at release level 37 . ± Customizing for individual customers leads to poor product maintenance in long run as product.Application Programming Interface ‡ What is API ± It is an Application Programming Interface ‡ Need of API ± Company cannot customize for every customer certain workflows or controls due to specific requirement of that client.

‡ API role in Site Administrator ± Prevention of Multiple Login ± Changing programmatically Site configuration Settings ‡ Example ² Changing the attachment size for particular mail from default 3000KB ‡ Changing the mail format from html to text or vice versa ‡ Getting information on how many connections are used and type of license used 38 .API Contd. ‡ How API helps end customer? ± API allows customer to program there own logic within a release and can be migrated to any new release they receive from the company.

API ² Quality Center ‡ API role on Quality Center ± Control to their workflow for any module ± Customizing forms for any individual groups or users ± Can create dependency or trigering alerts for specific incident at all module level ± Customizing Default Selection in list box for any users or groups 39 .

Comments & QueriesQueriesQueries are always welcome.com 40 .com Or webinar@softsmith. Send emails to: sriramank@softsmith.

com Thanks & Happy Testing. It will help us to improve in next sessions.FeedbackFeedback- Please spend few minutes from your valuable time to provide your feedback.. 41 . Contact Details Sriraman K Email : sriramank@softsmith.

Sign up to vote on this title
UsefulNot useful