The integration point of Stream Test Pro™ and any Functional Testing Tool will be successful as long as they support Windows IDE and OS.

All User Actions are recorded in the Functional Tool to drive the user actions against your target application. The Functional Tool then sends a single-line-request to Stream Test Pro™ to perform specific functions i.e. UI Validation (‘FEND’) and Database Validation (‘BEND’).
 

All activities carried out by Stream Test Pro™ are stored in the STP Database then renders to STP Client for user management. The  scripts built in the Functional Tool are embedded around the framework to validate your target application. Find below examples, of ‘Single-Line-Requests’ from your Functional Tool to STP.

‘Single-Line-Request’ from QTP to STP API to export the required data for validation from the CRGS database
testpoint.ExportSQL((sql), (sBendPath),(sFileName1), (","),("txt"))
 

The database validation logs are stored in the STP Database, and rendered to user via STP Client, as seen below. STP will determine if the Database Validation has passed or failed based on discrepancy found. It will launch the editor below for user to validate the discrepancies.
 

Implementing Performance Counters from Functional Test Tol measuring response on CRGS application
testpoint.start_timer((1),(11),("c_ModelTree_TCMODBT0002"),("CRGS-R1"),("MODELTREE"),(1))
testpoint.stop_timer((lPerTestID),(counterid),(sBuild),(sLog),(1))

The user can define via STP Client specific areas in the CRGS application to be measured for User Experience, i.e. how long it takes for the system to reply when the user invokes the ‘CREATE’ button. The performance results is then logged and stored in STP Database and rendered via STP Client.

See below for a screen shot of the trend of a particular counter across many runs.
 

Validating UI Objects on the CRGS Application, comparing them to expected results, capturing screen-shots of the image, then send it to STP for viewing.
testpoint.SendAutoTests((iResult), 0,(l,TestCaseID),(sLogOutput), (sScriptName) ,(sBuild), (sEnv), (sLog), 1)

The test logs are stored in the STP Database and again rendered to STP client. Below is the Log Manager window that allows user to walkthrough test logs with its associated screen shot for verification. The user can add notes to each individual log item, raise defect and update statuses with appropriate comments. Logs can be easily shared with stakeholders and team members via internal STP email and export capabilities.

"Overall, STP is the perfect tool for Regression Execution Management. In all my consultation career, I haven't come across Management Tool that incorporates & blends very well with other leading automation tools". Test Automation Consultant