UFT Training in Chennai | QTP Course

Every UFT script is VBScript. So we start here — not with the tool, but with the language. This module is designed specifically for testers, not developers. We cover only what you actually use in UFT scripts. If you’ve never coded, this is your start. If you code already, you’ll be through it in two sessions.

• Variables, data types and constants in VBScript — how UFT uses each
• Conditional statements: If-Else, Select Case — with real test scenario examples
• Loops: For, Do While, Do Until — iterating through test data and UI elements
• Procedures and functions — building reusable VBScript components
• Built-in functions: string manipulation, date/time, type conversion
• File system operations — reading test data from external files
• Excel object model — reading and writing test data in spreadsheets
• Error handling: On Error Resume Next, Err object — writing scripts that don’t die silently
• Hands-on: Write 10 VBScript functions that cover real QA automation use cases

By the end of this module you’ll have written and run actual UFT tests against real applications. We install UFT from scratch in the first session — so you understand the environment you’re working in before you write a single line.

• UFT One architecture — how it communicates with applications and browsers
• Installation and licensing — common setup issues and how to fix them
• UFT interface: test pane, data table, active screen, results viewer
• Recording modes: normal, analog, low-level — when each is appropriate
• Running and debugging your first recorded test
• Understanding generated script — what UFT creates vs what you should write manually
• Record and playback limitations — why you can’t just record everything
• Hands-on: Record, edit and run three tests on live web applications

Bad object identification is why most UFT suites fail. We dedicate a full module to this because it’s where quality UFT engineers are separated from ones who produce brittle scripts. If objects aren’t identified correctly, no framework in the world will save your suite.

• How UFT identifies objects — the property-value matching approach
• Object Spy — identifying, inspecting and verifying object properties live
• Mandatory, assistive and ordinal properties — when to use each
• Smart Identification — how UFT falls back when primary properties change
• Object Repository Manager — shared vs local repositories
• Managing objects: adding, editing, merging repositories
• Handling dynamic objects and changing property values
• Child objects and parent-child hierarchy
• Hands-on: Build a complete object repository for a multi-page application

A UFT test that doesn’t verify anything is just clicking through an application. Checkpoints are how you turn recorded steps into actual assertions. This module covers all checkpoint types — and more importantly, when to use each one and when not to bother.

• Standard checkpoints — verifying object property values
• Text and text area checkpoints — content verification on UI elements
• Bitmap checkpoints — when to use visual comparison and when to avoid it
• Table checkpoints — verifying tabular data in web and desktop applications
• Database checkpoints — verifying data at the database level from UFT
• Accessibility checkpoints — UAT for enterprise compliance requirements
• XML and web service checkpoints
• Checkpoint pass/fail analysis in UFT results
• Hands-on: Add comprehensive checkpoints to an existing test suite

Hardcoded test data is the most common reason enterprise UFT suites become unmaintainable. This module teaches you to externalise data properly — so a single test script handles 50 data combinations without duplicating a single line of code. This is what separates scripts that work in a demo from suites that survive a year of production use.

• What parameterization is and why hardcoded values kill maintainability
• UFT data table — local and global sheets, how to use each
• Parameterizing tests from the data table — step by step
• External data sources: Excel files, CSV, databases
• Data-driven testing with multiple iterations and expected results
• Environment variables in UFT — managing config across environments
• Managing test data for positive, negative and boundary test cases
• Hands-on: Convert a hardcoded test suite to fully data-driven with external Excel data

Enterprise applications are slow. Pages load unpredictably. AJAX calls take different amounts of time on different machines. Synchronization is what stops your UFT suite from being an intermittent failure generator. We treat this as a full module — not a one-page mention in the middle of something else — because it’s where test suites live or die in production.

• Why synchronization failures cause most intermittent UFT test failures
• Wait, WaitProperty and Sync — when each is the right tool
• Exist and visibletext methods for dynamic content checking
• Handling AJAX calls and dynamic page content
• Browser navigation and page load events
• Timeout configuration — global and per-object settings
• Handling pop-ups: browser, Windows and application pop-ups
• Hands-on: Fix 5 intentionally broken tests with synchronization issues

This is the module that gets people promoted. Descriptive programming is what you use when the object repository isn’t enough — dynamic objects, objects without fixed properties, runtime-generated content. Senior UFT interviews almost always include a descriptive programming question. We make sure you can answer it with working code, not just a definition.

• What descriptive programming is and why the object repository is sometimes not enough
• Static description — hard-coded property-value pairs in script
• Dynamic description — using Description object for runtime property assignment
• ChildObjects method — finding and interacting with multiple matching objects
• Using regular expressions in object descriptions
• Handling dynamically generated tables, lists and grids
• Combining descriptive programming with the object repository
• Hands-on: Automate a dynamically generated order management screen using descriptive programming only

Most UFT courses show you the tool. This module is about building a framework — the architecture that makes a test suite maintainable when 20 engineers are working on it simultaneously. Keyword-driven testing is the approach that lets non-technical test analysts add test cases without writing VBScript. It’s also what senior candidates get asked about in every enterprise UFT interview in Chennai.

• What a test automation framework is and why it matters in enterprise projects
• Linear scripting vs modular vs data-driven vs keyword-driven — real trade-offs
• Building a keyword-driven framework from scratch: action words, driver script, data table
• Function libraries — creating reusable components that the keyword table calls
• Hybrid framework — combining keyword-driven with data-driven approaches
• Test configuration and environment management
• Reporting in the framework — test results that business stakeholders can read
• Hands-on: Build a keyword-driven framework for an e-banking application

UFT in isolation is useful. UFT integrated into HP ALM is how enterprise QA teams actually work. ALM is the test management platform for every large IT services project in Chennai that runs UFT. Not knowing ALM means not being fully productive on day one in any of those roles. We treat this as a full module — not an afterthought.

• HP ALM overview — projects, domains, modules: Requirements, Test Plan, Test Lab, Defects
• Connecting UFT to ALM — configuration and authentication
• Creating and managing test cases in ALM Test Plan
• Scheduling and executing UFT tests from ALM Test Lab
• Defect management — logging, linking and tracking from test results
• Generating test execution reports from ALM
• Jenkins integration — triggering UFT test runs from CI/CD pipelines
• Capstone project: Complete UFT automation suite for a multi-module enterprise application — object repositories, data-driven scripts, keyword-driven framework, ALM integration, Jenkins pipeline, GitHub repository
• Top 30 QTP/UFT interview questions answered live with context, not just definitions
• Resume review and GitHub portfolio walkthrough with trainer