This action might not be possible to undo. Are you sure you want to continue?
.............................2 Technical Framework of an Application Test Execution ..2....................................3. 6.....................6 4............ 5.....................2 List of Enhancements 7.............1 Functional Framework 4..........................2 Design Principles 2.......2........................1 Overview 7... 4..............2 Ease of Customization 2......................2 Application Setup 6...1 Maintainability and Extendibility 2..........10 7..........2............................................2..................... Introduction ............... Future Enhancements ...... 3.... 4 2........3 Customization and Preparation 6.........1 Overview 6.5 Viewing the Test Results...........................................AUTOMATION TEST STRATEGY USING FRAMEWORK DESIGN Table of Contents 1..........4 Guidelines .........3 Entry Criteria 2............................................1 Requirements 2.1 Auto run failed scripts 7...... 2....2 Data Synchronization Designed by santhosh Page 2 of 11 ............8 6..............6 Automation Architecture ..1 Flow 2.....4 Launching the scripts 6.............2...................2 Levels of Automation Test Scripts Current State ...................3 Definitions 2.......3........
This would imply that the design of individual elements be kept simple and intuitive. If the databases are refreshed. The only things that should change are the data tables. the automation team used the following principles to guide further design.AUTOMATION TEST STRATEGY USING FRAMEWORK DESIGN 1. ease of customization using Mercury Interactive’s QTP. This would imply building a common framework and standards on which more applications or test scenarios Designed by santhosh Page 3 of 11 . Guidelines Requirements The following were some of the requirements that were called out by the lights on testing team and by development team during initial design checkpoints. There should be an interface to select which environment is being targeted. it is essential to decide some key design principles that guide the rest of the design and helps make other design decisions quicker and in the right framework. There should be an easy way to select test scenarios at a more granular level in order set up more targeted regression. it should be possible to restart testing from the last executed test scenario. there should not be a need to changes the scripts. The scripts should be completely parameterized. 2. Analyzing the requirements. The scripts should work on all environments with little change. Design principles As with all designs. It should be easy to maintain and update the scripts with newer releases or changes done to the application. 3. Nomenclature of the scripts and functions is kept simple. 2. 1. In an event the machine on which the automated test suite is running crashes. Recovery should be built into the test scenarios. Introduction The purpose of the document is to describe a comprehensive framework for regression testing. Maintainability and Extendibility The automation regression test suite should be easily maintainable by the ongoing testing team. This Framework for Automated Regression Testing is built on principles of maintainability. The test suite also needs to be extendible. 5. 4.
Should be executed 2 to 3 cycles of manual testing. Entry Criteria Should complete full cycle manual testing. Application flows can be further classified into major and minor flows. Should be resolved all P0 and P1 defects. All applications and test scripts should strictly adhere to the framework and standards. The only things that could need changes during a setup of a test run should be a few constants and/or the data tables to setup the scripts with the right data. These major flows are identified by the co-ordination of both the test and development teams with the respective project managers and functional experts. The objectives of L1 test scenarios identification are • It targets to test the breadth and not the depth of the application • It should be used in place of sniff/stability testing Designed by santhosh Page 4 of 11 . A Flow is a unique sequence of major actions an end user performs to step through a given scenario.AUTOMATION TEST STRATEGY USING FRAMEWORK DESIGN can be easily added. Application should be stable in terms of performance and behavioral. A tester should not have to modify a test script in order to setup a test run. Definitions Flow During the creation of the regression suite an analysis was undertaken to better represent and separate out unique functionality from data combinations. Even with the constants and data tables. Sniff testing or testing all the major flows in the system with unique data combinations will henceforth be referred to as Level 1 testing or L1 testing. the changes should be easy and well defined. Levels of Automation Test Scripts Another objective in testing is to define varying levels of testing. all data should be parameterized into data files. Ease of Customization Given the nature of testing being highly data dependent. Thus arose the concept of Flows. Major flows with the right test data form a part of the sniff test suite. while both major and minor flows are used to fully test the whole application. In most development cycles there always exists the concept of a sniff test that is designed to be a quick preliminary check on the application versus the full functional test for the entire application.
semi-automated or would continue to stay manual. As the scripts execute. Current State During the design phase for all the modules/applications. call the functions to execute routine procedures and to obtain the data from the data files. Automation Architecture Functional Framework Before an application can be automated. End to End functionalities with the respective data combinations. General Functionality.AUTOMATION TEST STRATEGY USING FRAMEWORK DESIGN • It comprises of all major flows in the application • It comprises of only the essential data combinations • It comprises of all major failure scenarios Level 2 testing on the other hand will be the full functional test of the application. it is important to have the basic framework of an application in place. 3. The scripts while executing. Application Specific Functionality. The design process should identify automation candidates and put together various components of an application like:1. Technical Framework of an Application The init script initiates test execution for an application in Automated Regression Test Suite (ART). 2. The INIT file calls the function for user interface and also calls different scripts in the application. 4. the existing manual scripts were analyzed for the level of automation that could be achieved. When the Designed by santhosh Page 5 of 11 . The objectives of L2 testing are • Targets to test the breadth and the depth of the application (superset of L1) • Comprises of all major and alternate flows in the applications • Comprises of all data combinations (limited to a pre-defined set that ensures breadth and depth) • Comprises of all failure scenarios • Is based on existing test scripts • Should cover the long term business objectives in terms of ROI. they write the results into a log file that belongs to the INIT file. Based on this analysis the scripts were divided into flows that can be automated. 3.
Return data after reading the data sheet Functions (S) Function may call the data access data.Acess Data 2. the scripts log success and failure scenarios into the result file in INIT folder. Technical Framework – ART Diagram The result of all the scripts that are called by INIT file is logged into Result file. Execute routine procedures The function either: 1. Results The INIT file calls the function that generates the user interface. Scripts (S) Scripts call a function to 1. Data Sheet (S) QTP Scripts VBS Files Excel Files Excel / HTML Files Designed by santhosh Page 6 of 11 .AUTOMATION TEST STRATEGY USING FRAMEWORK DESIGN suite completes the testing. Execute the routine procedure for the script the final value. the results folder (containing the results log) presents in the INIT folder may be opened and the logs analyzed to obtain the test results. INIT file calls set of script files. INIT While executing. 2.
Test Execution Designed by santhosh Page 7 of 11 .AUTOMATION TEST STRATEGY USING FRAMEWORK DESIGN 5.
AUTOMATION TEST STRATEGY USING FRAMEWORK DESIGN Test Execution Flow Diagram Application Setup Customization and Preparation Automation Test Scripts Launching the scripts Viewing results Designed by santhosh Page 8 of 11 .
Launching the scripts 4. After this the tester needs to configure the path settings in the init and constants file to point to the location the scripts are being run from. 1. Viewing results 5. Along with this the tester should obtain the right version of the scripts from version control onto the local machine.3 Customization and preparation Designed by santhosh Page 9 of 11 .1 Overview This section gives an overview on what it takes to setup and execute an automated test run. 5.2 Application Setup During this step the tester needs to ensure proper setup of QTP on the machine the scripts are to be executed. Customization and preparation of Automation Test Scripts 3. Application Setup 2.AUTOMATION TEST STRATEGY USING FRAMEWORK DESIGN Application Setup Customization and Preparation Automation Test Scripts Launching the scripts Viewing results 5.
AUTOMATION TEST STRATEGY USING FRAMEWORK DESIGN At this step the tester selects the scripts to be executed and the data combination to be used during execution.4 Launching the scripts As a last step the scripts are launched from Test Director. At the top of the window. This will open the test results window. click on the view test results button in the QTP. Labeling the test run 2. This step might also involve querying the databases to setup the right accounts and users in the data table. This is the most intensive step in preparation and should be planned in advance of an execution. Environment selection 3. Some of the front-end selections are: 1. The settings of the data table will vary from application to application Details of the data tables can be found in the data preparation documents for each application. a summary of the test results will be available. 5. L1 / L2 selection 5. Designed by santhosh Page 10 of 11 . Each application has a front end that is used to make overall selections for the run.5 Viewing the Test Run Results Once the test has run.
This section lists out the some of the suggestions that have been requested and suggested from both development and the automation team. The controlling procedures and functions that query these tables for valid test scripts and data combinations need to be changed to query for failed combinations.3 Data synchronization Setting up a test-run takes valuable time querying the databases for the right test data.2. there should be an option to easily rerun the scripts on the failed scripts and data combinations. During the setup of an automated run import the data into the data tables used by the scripts. The scripts then use the right data from the data-table for the test run.1 Auto-run failed scripts The test suite should record failed scripts and failed data combinations as the tests are being executed.2 List of Enhancements 6. Design Suggestion: The failed scripts and data combinations can be recorded in the excel data tables that record test activity. The process of synchronizing the data tables with what’s in the database can be automated as well making the setup process fully automated.2.1 Overview The current design and architecture lays the foundations to easily extend the application with requirements as and when they come from development.2 Common Front End Different applications have a different front-end to initiate the test-run. After a test run is complete. 6. The shouldn’t be any changes needed for the rest of the suite 6. Future Enhancements 6.2. Designed by santhosh Page 11 of 11 .AUTOMATION TEST STRATEGY USING FRAMEWORK DESIGN 6. This should be consolidated into a single front-end to launch various applications 6.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.