SQABasic Libraries

(Last Updated: Sep.10.2003)

The following lists the libraries currently under development with various versions of Rational's TeamTest product (Rational Robot). Robot V2000 and beyond can use these libraries without issue. The libraries must be compiled with the version of Robot that will run them.

These are generally application independent libraries that are useful in an overall scheme of automated test with SQA Robot.  They are constantly being enhanced and refined and new libraries appear fairly often.

General Libraries, DD Utility Libraries, DDEngine Libraries, Component Functions

Consult the Data-Driven Engine Reference for a ready reference on DDE setup, commands, and syntax. (650K+)
Consult the RRAFS Detailed Reference for a newer version/format of similar information (small downloads). Consult the RRAFS Quick Reference for a single list of ALL supported action commands.(80K)

General Libraries:

• ApplicationUtilities Application-scope Utilities (Launch etc.)
• BufferUtilities Helper Utility for custom buffer/stack types.
• CWPHooker DLL Library for Popup Menus.
• DatabaseUtilities for accessing ODBC databases.
• ExcelUtilities Excel Automation Server routines.
• FileInfoFIFO A custom Buffer type using BufferUtilities.
• FileTestUtilities: For testing files and directories (needs work).
• FileUtilities: General Purpose File Utilities.
• ImageUtilities: Robot Image Capture and Compare.
• LogUtilities Implements multipoint logging.
• MenuUtilities for working with Menus and Popups.
• NTCommandUtilities use some DOS-based commands.
• ProcessContainer to See GUI Children and Properties
• Publish to extract and publish HTML doc on all this!
• STAFUtilities STAF access functions. STAF Home Page
• StringUtilities String parsing functions.
• XMLUtilities XML parsing and creation.
• WIN32 API Header info for using the Win32 API.
• WINRegistryUtilities Access the Windows Registry.
• WIN32Utilities Routines using the Win32 API.

Utility Libraries specifically intended for Data-Driven Automation:

• Using Custom DDE Extensions for site-specific enhancements.
• CustomUtilities for custom DDE extensions.
• CustomRecordTypes for custom DDE Record Types.
• CustomDriverCommands for custom DDE Driver Commands.
• CustomLogUtilities for custom DDE Logging.
• CustomStatusUtilities for custom DDE test status tracking.
• CustomTestCommands for custom DDE Test Commands.
• DDGUIUtilities for working with Window objects.
• DDUtilities for getting information on Robot or the DDE.
• DDVariableStore for variables in scripts and data tables. See "How to..."
• StepDriverStack for making the DDEngine reentrant.
• SuiteDriverStack for making the DDEngine reentrant.
• CycleDriverStack for making the DDEngine reentrant.

The Core Data-Driven Engine:

• StepDriver. The low-level data driven driver.
• SuiteDriver. Intermediate-level data driven driver.
• CycleDriver. Highest-leve data driven driver.
• DDDriverCommands. Commands (C) available to all three drivers.
• Using DDVariables throughout the framework.
• Using Flow Control Commands within all three drivers.
• Using Custom DDE Extensions for site-specific enhancements.

ComponentFunction Script Libraries used by the Data-Driven Engine:

• GenericMasterFunctions Default Actions available to most ComponentFunctions that follow.
  
• CheckBoxFunctions
• ComboBoxFunctions
• ComboEditBoxFunctions
• ComboListBoxFunctions
• DatabaseFunctions
• EditBoxFunctions
• GenericObjectFunctions
• GraphicControlFunctions
• GroupBoxFunctions
• HTMLDocumentFunctions
• HTMLFunctions
• HTMLImageFunctions
• HTMLLinkFunctions
• HTMLTableFunctions
• JavaMenuFunctions
• JavaTableFunctions (in development)
• JavaTreeFunctions
• LabelFunctions
• ListBoxFunctions
• ListViewFunctions
• PopupMenuFunctions
• PushButtonFunctions
• RadioButtonFunctions
• ScrollBarFunctions
• SSTreeFunctions
• TabControlFunctions
• TreeViewFunctions
• VSFlexGridFunctions
• WindowFunctions

The above documentation was published in a completely automated fashion by developing the libraries with templates that allowed for in-context documentation that could then be post-processed for publication. The documentation is thus actually pulled right out of the source and header files and formatted for HTML publication.
See SQAPublisher and its GUI front-end Publish for more information.

Contact Carl.Nagle@sas.com if you have any additional questions.