(Click on the images below to view them in full size)

Dashboard Module enables a user to create customized reports. Knowledge of SQL and VB Scripting is required, as queries should be written in SQL for fetching the details of various modules in QC.

Here is a step by step introduction to Dashboard module.

1. Open QC application and provide the valid user name and password. Select the domain name and the required project name from the drop down list.
2. Click on the “Dashboard” module present on the left hand side corner of the application as shown below.
3. The window opens as shown above. We find two tabs in the menu bar “Analysis View” and “Dashboard View”.
4. Click on Analysis View and the user can find two folders by default “Private” and “Public”. A user can create the reports in private folder and only he/she can view the report and nobody else can look into the report present in private folder. A report created in public folder can be viewed by everyone who have access to the particular project.
5. Click on the New folder(Ctrl+Alt+F) option present below the menu bar to create a new folder.
6. Navigate on the new folder created and click on the new Item option present below the menu bar for creating a new report.
7. Once the user clicks on the option “New Item” four options will be available to choose. Select “New Excel Report” for creating a customized report.
8. Once the option “New Excel Report” is selected a pop up opens up asking the user to enter the name of the new report. Provide a name for the report as shown below.
9. Once the user clicks on OK a new blank report is created under the Test folder as shown below.
10. The user can view three options on the menu bar Details,Configuration and View
    • Details – This tab contains the name of the new report, Owner, Type of report etc.
    • Configuration – This tab contains the actual query, Post Processing section and all the other options for generating the report.
    • View – This tab contains the data and the report results of the report generated.
11. Under the Configuration tab we have three more sub tabs as mentioned below.
    • Query – Here the user can write SQL queries for every module
    • Post Processing – The user needs to write VB Scripts for getting the data received from the queries in a readymade fashion. For Example:- A user writes a query to get the defects logged by him/her but when the user runs the query an excel sheet is generated which gives data in a raw format.But with Post processing section a user can readily get the count of the defects logged without filtering the data in the excel sheet.
    • Generation Settings – This tab gives user the information of the path where the reports will be saved.
12. Click on “Query Builder” option present beside the Generate tab. The following tab opens as shown below.
13. The Entities present on the right hand side of the window are the table names and the corresponding field names. The user should pull the required table name and the fields required for generating the report.
14. As per the snap shot above, we have selected *(select all the fields from the table name) from Requirements table name which pops up all the field names present in the Requirements module.
15. Once the user clicks on “Run Query” the Query builder runs the query and gives the results to the user as shown below.
16. A user can perform the following operations:
    • Add Query – A User can add multiple queries by clicking on this option for different modules.
    • Delete Query – A user can delete the existing queries.
    • Rename Query – A query can be renamed by clicking on this option.
    • Test Query – This option is used to test a query for a limited set of values (max 10).
    • Run Query – This option is used to test a query for all the values present in the particular module.
17. A user should write the VB Script in the post processing section for generating a readymade report.
18. This is a sample report generated after inputting the query and the writing a VB script in the post processing section.
    

With that we come to the end of Dashboard module. I hope you like this article.

If you’re planning to take Quality Center Certification, don’t forget to check our mock QC certification questions.

All About Dashboard Module of Quality Center is a post from: Learn QualityCenter (QC)

Defects Module of QC helps a tester in logging defects when any issues are found in test case execution.

Here is a step by step introduction to this module. (Click on the images below to view them in full size)

1. Log into the Quality Center with your user name and password. Select the domain name and project name.
2. Click on the Defects module present on the left hand side of the application.
3. When a new project is created the defects window will be blank – without any data.
4. Click on the “New Defect” (Alt+N) button present below the menu bar to create a new defect.
5. Once the “New Defect” button is clicked, a window opens up as shown below.
6. There are various fields such as Summary,Priority,Reproducible,Severity,Detected by, Description etc.The ones marked in red are the mandatory fields and they need to be filled by the tester.
7. The tester should fill in all the details for the new defect as shown below.
8. After entering the summary, we would now give a detailed account of the defect under description area
9. For a better explanation of a defect, we can divide it into following:
   1. Steps to reproduce:This would include the step wise reproduction of defect, right from the login of the application being tested to the logout. It can also include:
      • The Pre-conditions required to reproduce the defect.
      • Test Data required to reproduce the defect.
   2. Expected Result: This includes the expected system/application (under test) behavior as opposed to the defect (Actual result). It can also include:
      • Design document references.
      • Requirements document references.
   3. Actual Result: This includes the current system/application (under test) behavior as opposed to the expected result.

   

10. Severity/Priority: The most important of all is deciding the severity & priority of defect. When raising a defect, testers are often confused about the difference between defect’s severity and its priority. The dictionary speak the following:
    Severity – Causing very great pain, difficulty, anxiety, damage, etc.
    Priority - Something that is very important and must be dealt with before other things.
    The severity is the domain of the tester and they should be capable of recording this. For testers, severity is the impact of the defect on the application and their ability to continue testing. The priority is the domain of the business and should be entered by them against each defect raised to reflect the importance of the change to them. For instance, a spelling mistake would be deemed as a low severity by the tester, but if this mistake occurs in the company name or address, this would be classified as high priority by the business.
    To summarize:
    Priority = Business = Order of Fixing
    Severity = Tester = Failure of Application Above order of priority and severity can be changed to maintain consistency.
11. QC will auto navigate you to the previous screen (summary of defects screen), and here we would have our newly raised/logged defect with a unique defect id auto assigned by QC
12. The user (tester) can attach screenshots by clicking on “Attachments” tab next to “Description” tab
13. Click on “Attach” section and add the snap shots for the corresponding defect logged as per the snap shot as shown below.
14. Comments can be provided in the Add comments section on the right hand side of the window.
15. Defect details can be viewed once the user double clicks on the defect as shown below.
16. There is a field on the left hand side “Linked Entities”. Here a user can link similar defects created for different platforms. Example: A tester while executing a test case finds a similar issue across Win 2000, Win XP, Win 7 etc then the tester can log three different defects but link all the defects to each other so that a developer can fix all the defects at once.
17. The defect ID that was generated above should be supplied here for linking the defects to each other as shown below.
18. A user can navigate to any defect by clicking on the option “Go to Defect”. This option can be found on the “Defects tab” present on the menu bar.
19. You also have an option – “Send by Email” to send an email for the defect created.
20. Under the Menu bar we have an option to select the columns required to display on the defects window.
21. Once a user clicks on the “Select Column” field the pop up opens as shown below. A user can then select the required columns needed to be displayed on the Defects Window.

That is all about the Defects Module of Quality Center.

Please share this article with your friends by clicking on the Facebook “Like” button on the left side.

All About Defects Module in Quality Center is a post from: Learn QualityCenter (QC)

Here we will show the various features present under requirements module, in a step-by-step fashion.

You can click on the images below to view them in full size.

1. Open QC application and provide the valid user name and password. Select the domain name and the required project name from the drop down list.
2. Navigate to Requirements module present on the left hand side of the application. The snap shot is provided below.
3. Requirements are classified as User Requirements, Business Requirements and System Requirements.
4. Create a new folder by clicking on the “New Folder” option present below the Requirements menu bar.
5. Provide a name to the requirement folder and click on OK.
6. A new requirement folder is created successfully. Click on “New Requirement” button present beside the new folder.
7. A pop up appears, Provide the Requirement Type(Business,User,System) and Requirement Name in the edit box and click on OK.
8. Once the user clicks on OK a new window opens.Provide all the details in the fields specified.
9. The fields marked in red such as Category and Workstream are mandatory fields. Without providing values for these fields, a requirement cannot be submitted. Input all the other details such as Custom, Business Function, Bus/Tech etc and submit the requirement.
10. Once the user submits the requirement, all details inputted by the user will be displayed as shown below.
11. A user can create multiple child requirements by following the steps as mentioned above.
12. Requirements Traceability – Requirements can be traced in every project through the functions Trace From and Trace To.
    Trace From – Requirements that affect <Test1>
    Trace To – Requirements affected by <Test1>
    Find the snap shot below for more info.
13. A requirement can be converted to a Test. Right Click on the Requirement and select “Convert to Tests”.Find the snap shot below.
14. Defects can be added and linked to the requirements as per the snap shot shown below.
15. Attachments can be attached to a particular requirement.
16. Every requirement should be tagged to a release and a cycle. Consider an example given below for a release and a Cycle.
17. Consider a new project is started and it spans over a period of three months. This three month period can be tagged as a release and there may be many phases such as Analysis, Development, Deployment etc.All these activities can be tagged as cycles and requirements can be tagged to the cycles as a part of execution.
18. Navigate to Requirements present on the menu bar and click on “Assign to Release” and tag the particular requirement.
19. Navigate to Requirements present on the menu bar and click on “Assign to Cycle” and tag the particular requirement
20. If the requirement tree is very huge and user needs to find the requirement, a user can provide the requirement ID and click on “Go To Requirement”
21. A Requirement and its details can be sent via an email to the specified user. Navigate to Requirements present on the menu bar and click on the option “Send by Email”.
22. The Requirement view can be changed to three different views as mentioned below “Requirements Tree”, ” Requirement Details” and “Requirements Grid”. Requirement Details: Requirements Tree: Requirements Grid:

All about Requirements Module in Quality Center is a post from: Learn QualityCenter (QC)

In this article we’ll see how we can run automated QTP scripts from Test Lab in QC.

Before you try to run your automated scripts from test lab, you need to make sure that your tool (QTP/ WinRunner ) is connected with Quality Center. Here are the steps to connect QC to QTP.

First you need to ensure that  Allow other Mercury products to run tests and components option present under Tools > Options > Run in QTP is checked.

If you are running the tests on the same computer where you have QC client installed, then you will need:

• QTP Connectivity Add-In
• QTP Add-in

If you are running the tests on the different computer than where you have QC client installed, then you will need:

• QTP Add-in where QC client is installed.
• QTP Add-in and QC connectivity Add-in where QTP is installed.

QC connectivity can be found at QC server URL > ‘Add-Ins Page’ link > ‘QC Connectivity’ link > ‘Download Add-in’. QTP Add-in can be found at QC server URL > ‘Add-Ins Page’ link > ‘More QC Add-ins’ link > Download and install QTP Add-in according to its version.

We will now see how to execute the automated test scripts from the test lab module. (Click on the individual images below to view them in full size, press ‘Esc’ key to return)

Navigate to Test Plan module in QC.

Create a folder under the root folder and right click to create a new test as shown below.

Once New test option is clicked a pop up appears as shown below. In the Test Type box, select QUICKTEST_TEST to create a Quick Test Professional test, or select WR-AUTOMATED to create a Win Runner test.

In the Test Type box, select QUICKTEST_TEST to create a Quick Test Professional test, or select WR-AUTOMATED to create a Win Runner test.

Once Test Name is provided and user clicks on OK.It takes to the next step where we need to provide the description as shown below.

Once the user clicks on OK, a test is created as shown below.

Once the automated test case is created. Click on Test Script tab present on the right hand side.A script is generated based on the design steps of the test case as shown below.

Navigate to Test Lab module present on the left hand side of the application.

Navigate to the folder created and add a test set “Test” as shown below.

Right click and select the option “Select tests” which open a test plan tree as shown below.

Select the tests from the test set by clicking on the left arrow in the test plan tree present on the right hand side.

The selected test will appear in the test set.

Select the required test case and click on the “Run” button present on the top, below the menu bar.

The automatic runner pop up opens up, where the test to be run will be selected. Then click on Run.

This connects to the automation tool which is integrated with the QC application and gives us the result of the run for the particular test case.

When a test has finished running you can view the test results in your selected testing tool

• To view the test results in Quick Test Professional, click the ‘Launch Report’ button.
• To view the test results in Win Runner, click the ‘View Report’ button.

Test Lab Module in QC Part3: Running Automated Scripts from Test Lab is a post from: Learn QualityCenter (QC)

In this article we’ll see how we can raise a new defect from the test lab itself for a particular script. (Click on the images below to view them in full size. Press ‘Esc’ key when you wish to return to the article)

Once you find a particular test case is a failure and you’re sure it’s a defect, then follow the steps mentioned below.

1. Click on the option Run –> Select Run Manually from the drop down list.
   
2. Click on Begin Run as shown below.
3. If any/all steps are failing for a test case then update the status as Fail Selected/Fail All as per the snapshot shown below.
4. Once the status is updated as “Failed” click on the “New Defect” option present beside the attachment section.
5. A new window opens. You would need to input the details of the issue in various fields given below and hit Submit.

That’s it, a new defect will be logged in the system.

In the next article we’ll see how to run automated test scripts from the test lab module.

Test Lab Module in QC Part2: Logging Defects from test lab is a post from: Learn QualityCenter (QC)

This is a series of articles on Test Lab module in Quality Center. In this series we’ll see how to create test sets, how to load test scripts from test pan to test lab, how to manually run those scripts and how to run those scripts using automated tools provided by HP. (You can click on the images below to see them in full size)

How to create Test Sets and load test scripts from Test plan module to test lab module?

[Pre-requisites: All the test scripts should already be uploaded to the test plan module]

Creating a new test set

Click on the Test lab icon on the main menu bar. It will open the Test lab module as shown below. Right click on the concerned folder in the Test lab tree and click on New Test Set as shown below.

A pop up window appears as shown. Fill in the “Test Set Name” and click on Ok button.

Another pop up window appears. Provide the description.

A new Test set will be created under the selected folder as shown below

Moving Test scripts to Test lab from Test plan

Select the test set created and right click.We can look into an option “Select Tests”. Click on the option.

This opens up a Test Plan tree as shown below.

Select the test set and the test cases which needs to be moved to the test lab

All the Test scripts present in the selected Test Set of the Test Plan tree will be moved to the selected Test set in the Test Lab as shown below.

Multiple test cases can be pulled from the test plan tree to the test set as shown below. Select the folder which needs to be pulled. A pop up appears to confirm the test case pulling from Test plan tree. Click on Yes and all the test cases will be moved to the test set.

Running Test Scripts manually

We will now see how to execute test scripts from the test lab.

Select the Run button as shown in the screenshot below.

When Run Manually is selected, the manual runner Pop up window will be displayed

The Manual Runner screen will display all the steps in the script.

Select ‘Attach To Step’ from the Attachment dropdown if any attachment is to be uploaded.

Any number of attachments can be uploaded (might be snap shot, doc, code snippet, errors etc) to the step for a particular test case. The maximum size of an attachment would be 5 MB. Once the attachments have been attached, you can close the attachments section.

Click on ‘End Run’ once the status is updated and attachments have been uploaded.

The main QC page opens with the status of the test case changed to Passed.

There are a few criteria’s defined below for the status field of a particular test case.

1. If all the steps in the test case pass then we can readily select ‘Pass All’. This updates all the steps of a test case to Pass.
2. If any step in a test case fails because of an issue then we can go into the step and update the status of the step to be ‘Failed’.
3. If any step is left as ‘No Run’ in a test case, the test case status will get changed to “Not Completed”.

When end run is clicked the status of the test case will be changed as shown below.

In the next article we’ll see “How to raise a new defect from inside test lab.”

Test Lab Module in QC Part1: Creating test sets, loading test scripts and running scripts manually is a post from: Learn QualityCenter (QC)

What are the major changes between QC 10.0 certification exam and QC 11.0 certification exam?

Instead of Quality Center(QC) Software v11 it will now be known as Application Lifecycle Management(ALM) Software 11. In QC 10.0 and earlier versions you need to take both QC exam(HP0-M31) AND QTP exam(HP0-M39) to get AIS certificate from HP.  Starting with ALM 11, you just need to take one core exam that is HP Application Lifecycle Management 11.x Software (Code HP0-M46). (Informally known as QC 11 certification exam)

What to expect in HP0-M46: HP Quality Center 11.0 exam?

• Number of items: 67
• Item types: multiple choice, drag-and-drop, and point and click
• Exam time: 105 minutes
• Passing score: 74%

[Source: HP ALM 11 exam preparation guide]

What is the syllabus for ALM 11 certification exam?

Please check the table below.

How to enroll for QC 11 certification?

Here are the steps you can follow to register for HP Application Lifecycle Management 11.x Software. Code for this exam is HP0-M46.

With effect from Feb 1st, 2012 HP certification exams are conducted by Pearson VUE. You need to apply for HP learner ID here. Once you have the Learner ID, you can then proceed to create your user profile at Pearson VUE.
Exams can be purchased using credit cards/PayPal or Wire transfer. The country specific price list can be found here.

How to prepare for QC 11 certification?

To prepare for QC 11 certification, you can take help of our high quality QC Cert mock questions engine. These papers are developed by experts of QC in collaboration with Learn Quality Center

QC Cert is a set of 226 questions. QC Cert will not only help you ace QC 11 certification exam but will also help you get a firm grasp over QC concepts. We have invested a lot of time and energy to come up with these questions and have tried to incorporate almost all major concepts of QC and syllabus of QC 11 certification inside these papers.  Check more details here.

Details on QC 11 Certification (HP0-M46) is a post from: Learn QualityCenter (QC)

The Document Generator enables you to create a hard copy of the data contained in a Quality Center project. You can select information from the Quality Center modules. For example, from the Test Plan module, you can choose which folders and tests to include from the test plan tree, sort this data alphabetically or in a custom sort order, and display the data as lists or tables.
We are going to be exporting for this article the test cases that are in the folder “Flight Reservation” in Test Plan module.

Follow these steps:

Step 1. Locate Test Case path in Test Plan Module.

Step 2.Open Document Generator window

To start the Document Generator, click the Tools button on the upper-left of  the Quality Center window. Choose Document Generator. The Document
Generator opens.

Click on Document to set formatting instructions that control how the document will look and what is included in the cover page. By default, the Document link is selected in the Document Generator tree and the Document Settings tab is displayed

Document Setting tab type a title for the document, Author Details, Initial and email address and description of the document. These information are optional.

Options tab, select what you want to include or see in your document. For example, , create a table of contents and an index, and place test scripts and file attachments in the text of your document.

logo tab, you can load image from file, unload image that you would like to display in your document.for example, you can print a company logo on each
page of the document.

Customization You set formatting instructions in order to determine how your project document will look.

Step 3. Test Plan

Since the information for the document that we want to generate is located in Test Plan, we have to select  Test Plan and expand the Test Plan node in the Document Generator tree.

Expand the Test Plan node in the Document Generator tree. Select the Subject Tree check box and click the Subject Tree link. The Subject Tree
page is displayed

Step 4. Subject Tree

You use the Subject Tree pages to specify the information from the test plan tree view of the Test Plan module that should appear in the project document.

Select the Subject Tree check box and click the Subject Tree link. The Subject Tree page is displayed

Determine the order (Alphabetical or Custom) under Tree Sort. In our case select Custom.

Specify  under Folders, which test plan tree you want to include (All or Selected).

Choose Selected to export just the test cases contained in folder Flight Reservation from the Test Plan tree structure on to the right pane

Select attachment if you want to include in the document.

Page break after each folder to insert page break in project document  after each test folder subject.

You can also include graphs by selecting Graphs.

Step 5. Subject Tests

You use the Subject Tests pages to specify the information from the test plan tree view of the Test Plan module that should appear in
the project document

Under Tests select Selected, Design steps and click on Filter & Sort Button to bring up Filter window.

On filter Condition Tab, look for Subject field Name and hit the button in filter condition column.

This will bring up Select Filter Condition Window. As you can see it has Test Plan tree structure.

Click OK button to go back to Filter Window. As you can see, now Subject field has a value in Filter condition column.

Hit on OK button to return to Document Generator Window.

Under Layout select Full Page or Tabular.

To include test scripts in the document, select Test scripts.

If you use Business Process Testing, you can include the layout of the components included in the tests. Select Components detailed layout and
choose what to include in the detailed layout:

• To include component steps, select Component steps. Click the Customize button to open the Tabular Layout dialog box to customize the component steps table. Use the Tabular Layout dialog box to choose the defect columns that will appear in the table, and to set the column order, width and captions.

• To include the iteration list, select Iterations list.

To include test attachments in the document, select Attachments.
To display a list of all the changes made to the tests, and which user made each change, select History.
To insert page breaks in the project document after each test, select Page break after each test.
To include a table of linked defects, select Linked defects. Click the Customize button to open the Tabular Layout dialog box to customize the
linked defects table. Use the Tabular Layout dialog box to choose the defect columns that will appear in the table, and to set the column order, width
and captions. You can also specify whether to display only defects that have been directly linked to tests or to include indirectly-linked defects as well.

Step 6. Test List

You use the Test List page to specify the tests from the Test Grid that should appear in the project document. For more information about the Test Grid.

Expand the Test Plan node in the Document Generator tree. Select the Test List check box and click the Test List link. The Test List page is displayed. Repeat the steps from step 5.

Step  7. Add to Favorite

After you have set the formatting instructions and specified the document’s content, you can save the document settings as a favorite view for future use
and generate the document.

Click in Add to Favorites button, Add Favorite dialog box opens, enter a name in the name box and set the location as Private or Public and hit the OK button to return to Document Generator Window.

Step 8. Generate the Document

After you set formatting instructions and specify project data, you can generate the project document. You save the document as a Microsoft Word file.

Tip: You can generate a preview project document that enables you to quickly see how the document will look, without all the detail included. To generate a preview project document, click the Preview button. Quality Center opens Microsoft Word and displays the preview project document.

To generate a project document:

• If there are open project document files from previous runs of the Document Generator, close the files.
• Click the Full Document button. The Save As dialog box opens.
• In the Save As box, set the location for the document in your network file system.
• In the File name box, assign the document a name.
• Click the Save button.

Quality Center begins generating the document and a dialog box displays document creation progress. To cancel document generation, click the Stop
button.
When the process is complete, Microsoft Word opens and displays the document.
If the generated document contains links to attachments, a folder is created in the same location as the document, and the attachment files are copied to this folder. The name of the attachment folder is the name of the document with the suffix “_Attachments”. If you send the document to someone, you can send the attachment folder along with it so that the recipient can access the attachments by using the links

After document generation is complete, you can view and edit the document in Microsoft Word. The information for each module that you select is printed in a separate chapter of the project document.

Close Document Generator window to return to your project.

Export Test Cases from QC to Microsoft Word is a post from: Learn QualityCenter (QC)

Here is the updated URL to install HP Quality Center 11 (also known as HP Application LifeCycle Management ALM tool) 30 days trial on your machine.

Please follow ALL steps closely -

1. Go to Download Quality Center link
2. Click on the TRIALS AND DEMOS dropdown and click HP APPLICATION LIFECYCLE MANAGEMENT 11 EVALUATION
3. You will be asked to sign-in to HP Passport Single Sign On service. In case you’ve not registered earlier, complete the ‘New User registration’ form and you will be redirected to evaluation software terms of use. 
4. Click on “I Agree” button.
5. Assuming you are trying to download Quality Center for windows, click on Software_HP_11.00_Windows_TC096_15000.zip and Software_HP_11.00_Windows_TC096_15000.z01. You need to download BOTH the files in order to install QC. (In case you are downloading Linux/Unix variants you may need to download the appropriate versions as shown in the screenshot below)
6. The two files shown above are around 2.1GB in size so it will take around 2-3 hrs to download (depending upon your internet speed)
7. Make sure both files are present in the same folder and both files have exactly the same name except for the extension (.zip and .z01).
8. Download and install Winzip or WinRar. (7zip won’t work here)
9. Double click on the .zip file and you will see .iso file.
10. Extract this iso file using your favorite unzipping software.( I prefer a nice and free utility software called 7zip which can be downloaded here http://downloads.sourceforge.net/sevenzip/7z920.exe You can download and install this utility.)
11. Once extracted, go inside the folder TC096-15000\ALM and open Install.pdf  file.
12. If you are installing QC for learning purposes, you may just need to refer “Quality Center Starter edition” section. Go to “Installing Quality Center Starter Edition” section in the pdf file and follow the steps. The place where it asks you to use/insert CD, you can run the Setup.msi file present under TC096-15000\ALM\Installation\Win32 for 32 bit OS and TC096-15000\ALM\Installation\Win64 for 64 bit OS.

That’s it! QC should now be installed. All the best.

Step by step instructions to download and install Quality Center is a post from: Learn QualityCenter (QC)

You need to have a HP-QC user-id in order to  log in. Once you are logged in to HPQC do the following:

Step 1. From any Quality Center Module, select Menu Item Tools > Customize

The Quality Center – Project Customization screen appears after you select Menu Item Tools > Customize

Step 2. Select User Properties option.

NOTE : The list options depends on the Quality Center access privileges that your user account have. All users can use this option to change their user properties and password.

Step 3. In the User Property screen you will have to fill up the fields Full Name, E-Mail, Phone Number and Description with the required information.

Email information is very important because it enables you to receive email notifications and alerts directly to you mailbox, for example when a requirement is assigned to you or when a defects that you reported have been fixed.

Step 4. Click Change Password button

That will brings up the Change Password for [your Quality Center User ] dialog box, in this case [pru].

On the window shown below, enter your old and new passwords and hit the OK button to save your changes.

The change password dialog box closes. In the next dialog box click Save Button to keep the changes.

The Information window appear after clicking Save Button

Click OK button
On the upper-right side of the window, click the Return button to exit the Project Customization window and return to your project.

How to assign or change Password of Quality Center User Account is a post from: Learn QualityCenter (QC)