Explore topic-wise InterviewSolutions in .

Yes. We can schedule test by navigating to Goto >> Execution flow tab and selecting 'Test Run Schedule'.

Filter is used to view the data based on user criteria and Filters are available for Graphs, Reports and Grids.

Number, Date, String, List, User List, Look up list.

Creating Projects, Domains, Creating and managing Users, Track user limits etc.

HP UFT/QTP Tests, Manual Tests, HP Load Runner/Win Runner Scripts.

A library represents a collection of entities in a ALM including their relationship to each other A library also allows one to collect the same entities as in versioning.

No, Not Covered status meant for requirements for those tests are neither created nor mapped while Not Run status means for requirements that are yet to be executed

Requirement Module Reports, Test Plan Module Reports, Test Lab Module Reports, Defects Module Reports.

a copy of test case that contains various test steps.

The results are always stored in Test Runs Tab of Test Lab Module.

Manual or Automated Tests can be executed at a specified date and time.

Defects can be linked to Tests, Test Steps, Run and Run Steps, Requirements.

Follow up entities can be created on Test Plan, Test Execution Grid, Defects grid.

The Graphs, Reports, Live Analysis Graphs are available in HP ALM.

The predefined groups are Developer, Project Manager, QA Tester, TD Admin, Viewer.

We can add either a parent requirement or a child requirement against a test case in ALM

It is a feature in HP Sprinter using which we can enter data into the application. We can insert multi-set of data directly into the application with respective matching fields all at once.

Sprinter is manual testing utility that is integrated with HP ALM more effectively. It helps us to record and fast farward manual testing. It also allows testers to log defects from Sprinter UI.

Dashboard consists of Analysis View, Dashboard View using which graphs are generated and analysed.

HP ALM modules are Requirement, Test Plan, Test Lab, Defect.

Defect Management Cycle can be customized using Project customization menu under Tools menu. Only Project Admins can customize and also we can make use of Script editor for the same.

Each product is deployed as many releases and a lot of cycles are associated with each release. Each release has a pre-defined scope and milestone associated with it.

HP ALM Workflow includes Release Specification >> Requirement Specification >> Test Planning >> Test Execution >> Defect Tracking.

ALM Editions are HP ALM essentials, HP QC enterprise edition, HP ALM performance center edition.

It consists of HP ALM Client(IE Browser), ALM Server, Database server.

Coverage status is percentage of testing covered at a given time and also to keep track of project deadline.

You can store requirements in ALM to ensure 100% coverage, for change management and also for tracking purposes.

Testers can switch between ALM projects by navigating to Tools >> Change Projects >> Select Project.

HP UFT can be used in conjuction with HP ALM using the add-in HP ALM − UFT addin

HP ALM supports MS SQL and ORACLE

Once a test is executed the status of the tests are automatically saved when the user clicks on "END RUN" button in the Test Lab

Yes. ALM supports Business Process Testing (BPT) in which Subject Matter Experts can create tests in a without involving in the Nitty-gritty of test case/script designing.

Yes. Select the tests that needs to be exported and perform Right Click and select "Save selected" or "Save All" and enter the file name to be exported to excel.

Yes. Using the MS Excel/Word Plugin.

The Execution status of a test case can be − Pass, Fail, Blocked, No Run.

The Defect ID is automatically generated after clicking Submit button.

In the defect tracking window of ALM, there is a “find similar defect” icon. When this button is clicked after writing the defect, if anybody else has logged a similar defect then the system points it out.

Test data can be stored in a seperate file(say excel sheets) and uploaded along with the test cases or it can be maintained under parameters tab of a test case.

A Test Case is imported from Test Plan module to Test Lab module for execution under a test set known as test instance. Sometime it is okay to have multiple instances of the same Test Case in the Test Lab Module.

Test Lab is the module where we execute the Test Cases that we developed using the test plan Module. Both Manual and Automation executions happens in the Test Lab.

If a requirement depend on other requirement then treating Child requirements to the main requirement you can evaluate the sub requirements related to the main requirements.

Test management tool enables testers to create, execute and log defects while defect management tool helps us to create and track defects only.

Yes we can create UFT test from ALM but we must first make sure UFT has the ability to execute tests from ALM.

Version control is change management tool which helps us to keep track of changes made to entities in our project including requirements.

The Quality Center modules are − Management Module, Requirement Module, Test Plan, Test Resources, Test lab, Defect Module, Dashboard

ALM was formerly known as Quality center, a popular test management tool which is developed using J2EE with backend as MSSQL or ORACLE. It is a web-based tool and supports communication and association among various stakeholders. It also integrates with QTP , WinRunner & LoadRunner. We can also create reports and graphs for Analysis and Tracking for Test processes.