Best Practices for Robust UFT Frameworks

Quick guide: structure, error handling, and reusability.

1. Framework Structure / Architecture

Modular Design with Actions

🎥 Video: UFT UAI – Descriptive Programming in Function Libraries

• Use Reusable Actions for recurring business processes (e.g., login, navigation).
• Limit the number of actions per test to avoid performance issues.
• Each action should follow Single Responsibility.

Layered Architecture

• Test Layer: test logic (what to validate).
• Business Layer: business operations (e.g., "create customer").
• UI Layer: object handling (Object Repository or Descriptive Programming).

Object Management

• Use a Shared Object Repository (TSR) for centralized management.
• Use Descriptive Programming for dynamic UI elements.

Data Management

• Data-Driven Testing: use UFT DataTable or external sources (Excel, DB).
• Separate test logic from test data.

CI / Execution

• Integrate tests into CI/CD pipelines.
• Execute tests in parallel or batches to reduce runtime.

2. Error Handling (Robustness)

Error Handling

• Use On Error Resume Next carefully and validate Err.
• Log errors using Reporter.ReportEvent and reset with Err.Clear.

Recovery Scenarios

• Use UFT Recovery Scenarios for popups and unexpected failures.
• Define trigger → action → post-recovery clearly.

Synchronization

• Use WaitProperty, Sync, or Exist.
• Avoid fixed Sleep statements.

Logging & Reporting

• Capture screenshots, error messages, and context.
• Use structured Reporter events (Pass / Fail / Warning).

3. Reusability & Maintainability

Function Libraries

• Store reusable VBScript functions in shared libraries.
• Organize by domain or UI component.

Naming & Standards

• Use clear naming conventions.
• Apply version control and code reviews.

Test Isolation

• Tests should run independently.
• Avoid shared state between tests.

Maintenance Strategy

• Plan maintenance cycles after UI changes.
• Track metrics: runtime, failure rate, flakiness.

4. Strategic Recommendations

• Training: ensure team alignment on framework standards.
• Feedback loop: distinguish test vs. application defects.
• Documentation: maintain clear architecture and onboarding docs.

ALM / Octane Integration in CI/CD Pipelines — integrating work items into automated releases

Orchestration, traceability, and automated test result uploads (UFT, API, Selenium).

1. Target Architecture

• CI/CD builds, executes tests, and writes results back to ALM/Octane.
• Automatic updates of stories, risks, defects, and test runs.

2. Integration Model

CI/CD → ALM (Bottom-Up)

• Pipeline triggers tests.
• Results pushed via API or plugin.
• Linked to work items automatically.

ALM → CI/CD (Top-Down)

• Octane triggers pipelines.
• Controls test selection.
• Manages quality gates.

3. Tool Integration

• Jenkins / Azure DevOps / GitLab pipelines
• UFT One / UFT Developer execution
• Automatic reporting to ALM/Octane

4. Governance & Quality Gates

• Minimum automation coverage
• No critical defects
• All pipelines must pass

5. Best Practices

• Clear mapping between tests and work items
• Consistent naming conventions
• Fully automated result uploads