Stream Test Pro™ is an Integrated Testing Framework Solution developed by Testpoint™ to deliver a low risk, high impact solution to organisations, looking to build from scratch or revamp their existing Software Test Automation Program to support and deliver on key Testing Requirements more rapidly, and significantly, contribute to its Software Development Life Cycle immediately.

Tpoint™/STP is built and employed on a ‘two-tier’ client-server architecture. There are key components that constitute the ‘make-up’ of the framework which are briefly defined below.

• STP Client. STP User Interface.
• STP ATSI™.  The Automated Testing Scripting Interface (ATSI™) defines the integration and interaction of any Functional Test Tool with the framework. The ATSI provides fundamental and advanced functions and methods to allow any Functional Test Tool to send ‘Single-Line-Request’ to STP.
• STP Database. STP’s data warehouse can be built on any number of open source or commercial databases.
• 3rd Party Functional Tool. Any Functional Test Tool that supports Windows IDE and OS can integrate successfully with STP.

STP Client  – The client can be installed from any PC within the same network as the STP Database. The user will utilise the client for debugging/management of Test Runs/Results and provides the ‘live’ window to monitor the execution of tests. All testing results are dynamically published to the client and allows for immediate and appropriate actions by the user.

• Real-Time monitoring of Test Runs rather than post analysis.
• Ability to manage risks based on Dashboard Matrix i.e. Pass/Fail Rate & Performance Counters accompanied with Test Summary Notes,  allowing user to escalate appropriately when failures occur.
• Screen Shots are logged within STP and linked back to the associated test case/Test log.
• All database validations are also logged within STP and linked back to the associated test cases/test logs.
• STP provides the ability to drill down into discrepancies found with backend validation.
• Visibility on Test Results, and trace through to Test Cases, Defects, Test Suites, Builds and Configurations.

STP ATSI™ – The ATSI™ consist of the core underlying functionality and features of the framework. This allows the integration of ‘3rd Party Functional Tools’ into STP. The ATSI™ provides advanced and fundamental functions to assist the user significantly when developing tests. What this means, is that the developer is only required to connect to the ATSI™ with a ‘single-line’ of code to utilise these functions and hence, push their focus onto achieving business coverage rather than framework maintenance and development.  Some of these functions can be referenced at http://www.testpoint.com.au/support/guide/

STP Database –Having a dedicated database to manage your test assets gives you the following advantages:

• Eliminates the weight off the Functional Tool and focus on driving the tests without having to process results and therefore less work on CPU and Memory Utilization
• Most Functional Tools do not have a database component, i.e. all test results assets are either tool oriented and are stored in a file directory. With STP you can manage your data and build trends over time and provide references on-demand against any requested results.

3rd Party Functional Test Tool – The integration point of STP and any Functional Testing Tool will be successful as long as they support Windows IDE and OS. The Tpoint™/STP Framework is independent of the Function Tool. This means, that if an organisation is utilising more than one functional test tool, they can integrate with STP to provide a Single Point of Management and Reporting. On the other hand, if the organisation reviews its Tools Policy and decides that it needs to move to another Functional Test Tool , then the investment in STP is not lost, but rather, a win-win situation. This is achievable, as the core engine and management of results are handled in the STP ATSI™ and Database, the only change required will occur in the Tool itself, i.e. recapturing actions against the UI which is much more advantageous the trying to re-develop a framework that is specific to the Functional Tool. How will I benefit? 
Test Management, Open Source, Software Testing, MicroFunctional Tester, Quick Test Professional, Testcomplete