
Set up your HP ALM QC practice account by signing up for a free trial or downloading the setup, confirm email, then log in to access the project for practice.
Create and organize requirement folders in HP ALM / QC by adding high and low priority folders, and creating subfolders for modules like gambols email.
Create high-priority requirements within the HP ALM QC workflow by adding functional requirements to a compose email page, enabling attachment support and organizing them into folders.
Explore the requirement tab features in HP ALM / QC, including adding and deleting requirements, refreshing the window, and customizing columns and the requirement window and grid view.
Learn to set up folder structure in HP ALM / QC by organizing test plans into modules and testing types, including login and registration folders for guest and internal users.
Create test cases for login by a registered user, describe medium level testing with high priority, attachments, and a welcome message check using the formatting tab and test descriptions.
Create test steps for a login workflow in HP ALM QC, detailing design steps, adding and editing steps, and setting expected results like login page opens and a welcome message.
Learn how to link a test case with multiple requirements in HP ALM / QC, add or remove links, and have the test case cover the linked requirements.
Create a test set (test suite) in HP ALM / QC by building a release structure in the test lab and adding test cases to smoke and regression sets.
Learn to execute test sets in HP ALM / QC by selecting cases, running steps manually or via automation, and recording results to mark pass or fail during regression testing.
Link defects to test cases in HP ALM / QC by selecting the test case in the test lab and attaching the defect ID to the case.
Set and customize the test execution flow by dragging and dropping triggers to create and modify the sequence of test cases.
Explore the test run tab to view all test cases, their current status, and linked descriptions and execution details from the test lab.
Log a new defect in hp alm / qc by entering details, assigning severity and the assignee, describing steps to reproduce, and attaching evidence.
Explore how to attach data to a defect in HP ALM QC by using text file attachments, links, screenshots, system information, and clipboard data.
Explore viewing defect details, accessing attachments, and navigating the defect window. Configure column visibility and apply sorting by defect id or severity to organize the defect list.
Learn to manage defects in HP ALM QC by adding team comments, viewing defect history, flagging for follow-up, pinning favorites, and using text search to locate defects.
HP Application Lifecycle Management (HP ALM) is a set of software tools developed and marketed by the HP for application development and application testing.
It includes tools for requirements management, test planning and functional testing, performance testing (when used with HP Performance Center), developer management
HP ALM is designed to support key stakeholders responsible for delivering applications as they progress through their lifecycle.
It is a combination of a common platform, several key applications and a dashboard targeted at managing the core lifecycle of applications, from design through readiness for delivery to operations
We are going to learn following components
Project Planning and Tracking
HP ALM provides project planning and tracking so application development solutions teams can define, track, measure, and report on project milestones and key performance indicators.
Application Lifecycle Intelligence
HP ALM delivers real-time traceability of requirements and defects. QA department can significantly benefit from this traceability to get on-time reports and have visibility into the system under development
Lab Management Automation
HP lab management capability allows testing teams to provision and deploy a test lab themselves in a hybrid delivery environment
Asset Sharing and Re-use
HP ALM supports sharable asset libraries that can be reused across projects while maintaining traceability. Specific changes can be applied to shared assets for each project while maintaining library integrity, and projects can re-synch with the library as needed. Cross-project defect collaboration is also supported