Mosaic’s RSTAR Object-Driven Testing Framework
Why Object-Driven Testing?
Testing by its nature is highly redundant so the benefits from maximizing reuse are real and significant.
Not convinced? Watch our video – Why Full Reuse?
Then – let us show you how to achieve the available benefits!
Especially, if MS Word or MS Excel is still your test planning tool, let us show you how to move to a more powerful yet affordable framework!
Mosaic has combined the benefits of data-driven and keyword-driven testing utilizing the power of a database repository to implement an object-driven framework. The key component is reusable test data. As shown in the figure, three sample tests all reference ABC industries – test data replicated across three separate sheets. This is a common occurrence that can be easily improved by reusing the data in an object-driven framework.
Object-Driven Framework Objectives
The objectives of Mosaic’s object-driven approach are to:
- Reduce the cost of regression testing
- Ease needed maintenance
- Provide management visibility into testing process
- Minimize technical expertise required to automate
How the Objectives are Achieved
These objectives are achieved using the following techniques:
- Maximize Reuse: Higher levels of reuse mean that there are fewer testing assets (e.g., tests, test data, automation scripts) to develop and maintain, resulting in lower costs and quicker implementations.
- Separate the activities that require subject matter expertise from the activities that require technical expertise: Separating these activities means, for example, that the people automating the application do not also need to be subject matter experts. This reduces development and maintenance costs, and makes outsourcing much more productive.
- Design manual tests that can be directly automated: This makes automation much more practical and less expensive to develop and maintain.
- One Shared Repository: Since all test deliverables and execution results are integrated in one shared repository, the information management needs to make informed decisions is readily available.
The unprecedented level of reuse is enabled by the ability to reuse test data and the ability to dynamically bind test data to tests at execution time.
Mosaic’s testing framework includes the following components:
- RSTAR: RSTAR is a central repository for managing your testing assets including tests, test data, and the relationships of tests to test data and to automation scripts. RSTAR also includes test execution support, tracking of test execution results, defect capture and management reporting. (Mosaic’s Quality Center Solution uses HP Quality Center and Mosaic’s add-on to Quality Center, DSTAR, in place of RSTAR.)
- MSTAR® Object-Driven Architecture Repository: A comprehensive guide for building and automating reusable tests. Templates for writing reusable action scripts and master control programs to drive the automated scripts are included.
- Master Control Programs: Master Control programs (automation drivers) are available for many popular automation tools including QTP, Silk, and Selenium.
- Automation DLLs: DLLs are included for developing customized master control programs, accessing test data in RSTAR, and updating execution status and history in RSTAR.
Mosaic understands that you may have a significant investment in your current testing assets. You can start achieving the benefits of reuse without wholesale changes. We recommend the following approach:
Step 1: Import your data sheets into RSTAR. Your test scripts can use our DLLs to access the data from RSTAR.
Benefit: You will have your test data in one centrally accessible and maintainable place.
Step 2: For new tests, and where there is a benefit for existing tests, normalize your test data around the application, not the test.
Benefit: You will begin to get the benefits of reusable test data. The data can be used by all the tests that need it.
Step 3: Begin designing tests to be reusable.
Benefit: You will get the benefits of Full Reuse. There will be fewer test assets to develop and maintain. Your tests will be positioned for automation.