Test Automation Architecture (WinRunner)

Posted by Albert Gareev on Jun 15, 2007 | Categories: DocumentsImplementation

2-tier Data-Driven Test Automation Architecture (WinRunner)

Click to see full-size in a separate window

Business Components

Business Components – Functions that implement a certain business-case testing specific functionality which is used by Test Scripts. Typically Business Components are contained within compiled modules; that allows re-using the implemented logic in a similar Test Scripts. Business Components may incorporate standard WinRunner TSL functions and Service Component functions.

Business Components – Types

  • Testing Scripts / Data Maintenance Scripts / Comparison Scripts
  • Common Business Functions modules (environment and test setup functions, login components, business-specific verification components)


Service Components

Service Components – Functions that implement general (universal) testing functionalities not dependant on a specific application. Service Components are always contained within compiled modules. Service Components may incorporate standard WinRunner TSL functions and other Service Component functions as well.

Service Components – Types

  • API Functions for Win GUI / Web GUI steps, dynamic GUI recognition, on-screen data capture and verification
  • API Functions for processing data in Excel, text, XML files / memory arrays
  • API Functions for event managing, exception handling, recovery scenarios
  • Advanced Reporting Architecture (built-in within API functions)

  • Trackbacks

  • Trackback fromTest Automation Terminology - Automation Beyond
    Tuesday, 27 July, 2010

    […] Service Functionality – A low-level component in a layered automation framework (example); an implementation of generic, reusable functions (in object classes, function libraries, etc.) […]

Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
This work by Albert Gareev is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported.