1. APPLICATION LIFECYCLE MANAGEMENT(ALM) QUALITY CENTER(QC)
Consult America
Technology Consulting Services

2. ALM /QC What is software testing? Why testing is important?
Software testing is a process to identify and correct/fix any bugs/problems of an application or software.
In other words, software testing is an activity to check whether the actual results match the expected results and to ensure the software is bug free.
Why testing is important?
Software testing is very important because of the following reasons:
To point out the defects and errors that were made during the development phases.
To make sure of the Customer’s reliability and their satisfaction in the application.
Testing is required for an effective performance of software application or product.
It’s important to ensure that the application should not result into any failures because it can be very expensive in the future or in the later stages of the development.

3. ALM /QC What is manual testing ? What is the goal of manual testing ?
Manual testing is the process of manually testing software for defect.
What is the goal of manual testing ?
The goal of manual testing is to ensure that the application is error free and is working according to the functional requirements. Functional requirements means a requirement that is created for functional element. i.e.: there is no start menu in windows 8 version. So the start menu should be implemented in the next version of windows 10. so, building start menu is the main functional requirements of SDLC.

4. ALM /QC What is Quality Center?
HP Quality Center, a test management tool is now popularly known as Application Life Cycle Management Tool(ALM) as it is no longer just a test management tool but it supports various phases of the software development life cycle such as-
 Planning (initiation & requirements)
 Design  Development
 Integration & testing
 Implementation (production)
 Operations (maintenance & disposition)
 User Acceptance Testing (UAT) happens after production

5. ALM /QC History of QC? Quality Center was formerly known as Test Director, a product of mercury interactive. The below table provides us a better insights about the version history of QC:

6. ALM /QC What is ALM? Application Lifecycle Management refers to the capability to integrate, coordinate and manage the different phases of the software delivery process. From development to deployment, ALM is a set of pre-defined process and tools that include definition, design, development, testing, deployment and management. Throughout the ALM process, each of these steps are closely monitored and controlled.

7. ALM /QC Modules in ALM: Different roles of manual tester:
 Requirement: To track the customer requirements
 Test Plan: To store the test scripts and design the test cases
 Test Lab: To track the results and execute the test cases
 Defect: To track down the logged defects and log a defect
Different roles of manual tester:
There are 3 different roles of manual tester:
1. Site Admin: Site Admin is the actual owner. He can create Project Admin ,user. He can do anything like create, update, delete etc
2. Project Admin: Project manager is the Project Admin. He is assigned by the site admin for any individual project. He controls or owns project. A PA does not have the same privileges as Site Admin but he is admin of his project.
3.User: QA testers are assigned as user. They are like regular users. They have limited privileges. He can create certain things or do certain things that a PA gives him a permission to do. They are also responsible for creating test cases, test plans and execute the test, generating reports and retesting if needed.

10. ALM /QC As A Site Administrator: Installed Quality Center/ALM Software
 Create Domain-PIIT_TRAINING
 Create Project- PIIT_FORUM
 Activate Project
 Create Users for Quality Center/ALM
 Assign Users to the Projects
 Create Project Admin or making user as Project Admin for the Projects
 Create Password for the Users
 Delete User
 Create a User as a Site Admin
 Configure Wait Before Disconnect features
 Configure Mail Interval.
 Configure Mail Format.

11. ALM /QC As A Project Administrator:  Change Password
 Setup / Assign User to the Project
 Create New Users for a Project
 Add Existing user to the project
 Assign default Role / Privilege (TD Admin, Developer, Project Manager, QA Tester and Viewer) to the user.
 Set-up Groups / Create New Group role like Test Manager, Business Analyst, Test Lead, Configuration Manager, Program Manager etc.
 Change permission of the New Role
 Add Users to the New Role
 Customized Project Entities- Defect field customization i.e. making a field as a required field like making ‘Assigned to:’ field as required field
 Making ‘Status’ field as required field and adding statuses like ‘Fixed- Ready For Retest’, ‘Deferred’, ‘In Development’, ‘Retest Passed’, ‘Retest Failed’, ‘Works As Designed’ etc.

12. ALM /QC As A Project Administrator:
 Create new Project Lists i.e. Test Environment (DEV, ALPHA, BETA, PROD, QUAL, UAT) in defect window.
 Create new user field i.e. Test Environment (DEV, ALPHA, BETA, PROD, QUAL, UAT) in defect window.
 Create new Project Lists i.e. Putting Issue Type (Defect, System Change Request, Suggestions/Comments) in the Defect section.
 Create new user field i.e. Putting Issue Type (Defect, System Change Request, Suggestions/Comments) in the Defect section.
 Adding new items in the Project Lists i.e. add new sub-items in the Software item of Requirement Type field (Functional, Non-Functional, Software Change Request, Performance and UAT) etc.
 Configuring Auto Mail

13. ALM /QC As A Project Administrator:
Set Traceability Notification/Alert Rules
Traceability Notification Rules:
 Rule#1: When a requirement changes, notify the Designer(s) of the associated test(s).
 Rule#2: When the status of a defect changes to ‘Fixed’, notify the Responsible Tester of the associated test instance.
 Rule#3: When a test runs successfully, notify those ‘Assigned to’ the associated defects.
 Rule#4: When a requirement changes, notify the Designer(s) of the associated test(s) and all users.

14. ALM /QC As A USER:  Change Password
 Create Requirement folder in the Requirement section (Parent requirement)
 Create Child Requirement folder in the Parent Requirement section
 Enter Requirements in the Child Requirement folder
 Install Excel Ad-ins
 Prepare excel sheets for Requirements to export in the Requirement field
 Export Requirement using Excel in the Requirement folder
 Convert Requirements from the Requirement section to test in the Test Plan section
 Develop Design Steps or Test Cases in the Test Plan section
 Attach the Screen Shot / Documents for the steps, if necessary , for instanceTest Data needed like user id, password, doc, gif, jpg, jpeg, pdf, png, txt, zip, rar, exe.

15. ALM /QC As A USER:  Call Template to the tests
 Calling a manual test with parameters
 Perform Requirement Coverage / Traceability or Linking Test to Requirement in the Test Plan section.
 Prepare MS Excel sheets for design steps to export in the Test plan section
 Export Design Steps to export in the Test Plan section
 Create Test Sets in the Test Lab section
 Import test cases in the Test Set
 Execute Test Sets in the Test Lab section
 Log Defect in the Test Lab section
 Log Defect in the Defect section
 Attach the Screen Shot as an attachment for the Defect

16. ALM /QC
As A USER:
 Attach the Screen Shot using snapshot for the Defect
 Track / Filter Defect in the Defect section
 Enter comments in the comment section after re-testing the Bug like ‘Retest passed’ recommending to close this Defect or Re-test Failed, recommending to Re-open the Defect.
 Bug Life Cycle
 Generate Graph and Reports in the Requirement section
 Generate Graph and Reports in the Test Plan section
 Generate Graph and Reports in the Test Lab section
 Generate Graph and Reports in the Defect section-copy the graph and use it in the TAR-Test Analysis Report document
 Schedule automated test to execute or running automated test scripts in batch mod

17. ALM /QC Bug Life Cycle: Definition: •Bug: Bugs are errors/flaws that are found prior to production. •Defect: Defects are errors/flaws that are found after the production. Stage of bug life cycle:

18. ALM /QC URL (Uniform Resource Locator):
URL is an acronym that stands for Uniform Resource Locator and is a reference (an address) to a resource on the Internet.
localhost : localhost is a hostname that means this computer. It is used to access the network services that are running on the host via its loopback network interface. a localhost is always designated as

19. THANK YOU