“GENERIC SCRIPT” Everything can be automated, even automation process itself. “GENERIC SCRIPT” Everything can be automated, even automation process itself. ©Copyright © RASSWELL International Ltd. All rights reserved

Purpose of the Presentation The purpose of this presentation is to take a practical approach to Automated Software Testing and explain requirements for its success. The purpose of this presentation is to take a practical approach to Automated Software Testing and explain requirements for its success.Objectives Proof of concept and main principles of Keyword and Data-Driven Automation Testing Approach if compared to Regular Automation Testing Model. Proof of concept and main principles of Keyword and Data-Driven Automation Testing Approach if compared to Regular Automation Testing Model.

Regular Automation Testing Model Many organizations spend thousands of dollars on automation tools without considering training issues, software release deadlines and other factors. Since no one then has the training or time, the tools sit unused on a shelf, collecting dust. Business requirements/ Use Cases Done by BA Test Cases Implemented by QA/Testers Complicated Automated Test scripts Recorded/executed by Automation Specialist/ programmer Test Results Analysis, Reports, Bug Tracking Done by QA/Testers The full process MUST be repeated every time if BR/UC are updated. And Automation can ONLY be implemented after receiving stable version of the project (Environment-?).

Each Business Function requires a script. There may be hundreds of Business functions. But Automated Test Script Recording is time consuming as the process requires to create 1 Test Script per 1 Test Case (so, if there are 500 Test Cases then 500 Test Scripts are to be recorded); Object Data Repository must be created per test script/project and all the data in the file must be hard coded and changed manually every time when application’s objects are changed or new objects are added to the application. Manual Test Cases cannot be used directly in Automation, so changes in Manual Test Cases require updates in Automated Scripts accordingly by Automation Developer only. Disadvantages of Regular Model

Disadvantages of Regular Model (Cont’d) To implement a stable and comprehensive test automation project, Automated Test Specialist / programmer should understand ALL business rules of the project as well as the QA rules and objectives when analyzing Business Requirements and developing a Test Plan. Automated Test Specialist/programmer cannot start Test Script Recording until he or she obtains Test Cases from manual Testers and is given a stable software release of the project. Results created by any automation tool must be translated by a professional Test Automation specialist. Format of input/verification records must be strictly adhered to or the tests will fail.

Majority of Testers are involved in Manual Test Case development process; Manual Testers are not involved in Test Automation process. Automated Test Script Recording is time consuming and a Test Automation specialist MUST understand all business rules/requirements to create scripts. Lessons learned from Regular Testing model usage

The foremost factor in the long-term success of automated testing is very simple. If the code is maintainable, then it can be used easily throughout the project and be re-used for future projects. How to create automation that will be accessible to non- technical business analysts and is easy to use and maintain? Test Plan driven method is the most cost-effective: Requires a minimum of technical personnel, requires just ONE “Generic Script”, introduces the least amount of change for the manual testers. Developed manual Test Cases can be used for manual testing, and are automatically usable for automated testing Requires a minimum of technical personnel, requires just ONE “Generic Script”, introduces the least amount of change for the manual testers. Developed manual Test Cases can be used for manual testing, and are automatically usable for automated testing The decision is - Encapsulated test case. KEY TO SUCCESS!

GENERIC SCRIPT Create Generic source code allowing test cases to be written in a simplified table format. This approach is known as KEYWORD-driven, DATA-driven or even "third generation" automation. Benefits: Benefits: The numerous quantity of recorded Automated Test scripts will be The numerous quantity of recorded Automated Test scripts will be replaced by 1 Generic Automated Test Script/source code; replaced by 1 Generic Automated Test Script/source code; “Generic Script” developed to interpret and execute test statements according to Commands/test inputs specified in test cases (Example: EXCEL FORMAT) (Example: EXCEL FORMAT) Benefits: Benefits: One of the primary benefits of this architecture is that it allows tests One of the primary benefits of this architecture is that it allows tests to be specified in a format that is easy to write and review. It's well to be specified in a format that is easy to write and review. It's well suited for test teams with domain experts who may not be strong suited for test teams with domain experts who may not be strong programmers. programmers. “Generic Script” developed without having a defined functionality of a particular application. Benefits: Benefits: Test cases and Datapool can be completed later, when functionality is defined and implemented by developers. Test cases and Datapool can be completed later, when functionality is defined and implemented by developers.

KEYWORD AND DATA- DRIVEN Data-Driven : The data used by the automated test suite is pulled out into a separate file, which is used by the test script. Keyword-Driven: This is similar to data-driven, except keywords are used to indicate what steps the automated test suite should follow. Keywords are stored in a separate file.

Maintainability : KDD architecture allows tests to be specified in a format that is easy to write and review. Even with test automation, the manual test engineer retains the key role. Visibility: Test case in a script becomes simply a manual test case declaration, passing in required variables, and making a single function call. Test results and Analysis can be automated Advantages of KDD Model The main requirements for Test Automation design covered by “Generic Script” method:

Stability : Generic Script is more reliable, robust and easy to maintain, not dependable on business rules and function changes in project during iterative development process; Stability : Generic Script is more reliable, robust and easy to maintain, not dependable on business rules and function changes in project during iterative development process; Scalability: Automated Testing becomes more comprehensive and cost- effective. Test Cases Development and “Generic Script” script Coding can be performed as parallel and independent processes that save time and money for project implementation and testing. Advantages of the KDD Model

KDD Architecture “Generic Script” is based on recognition of CLASSES & OBJECT PROPERTIES that initialize according to COMMAND line in test case (key-word design). Parameters inserted in PARAMETER line are used as data input for the test case (Data-driven design). Test Step dataObject TypeMethod associated with Object Button_Click ButtonClick ECButton_Click ToolBar ButtonClick RadioButton_ClickRadioButton Click CheckBox_ClickCheckBox Click

Generic Automated Test Script Automated Test Library Calls of Custom- defined Functions Test Case 1 Test Case 2 Test Case 3 Application Under Test Keywords & Data Input Verification check-points Capture (Output) TEST RESULTS

Create Index –Test Scenario Open and read Test Case keywords – Test Case Commands keywords – Test Case Commands data -DATAPOOL data -DATAPOOL Find Application Under Test (AUT) objects by keywords and apply methods associated with objects and / or insert data assigned to the objects. Verify Application Under Test (AUT) checkpoints. Send output to Test Log Result file.

Test results and Analysis can be automated

TEST MANAGER  To simplify the usage of “Generic Script”  To create Test Scenarios  To modify Test Inputs  To see results saved in Excel/MS ACCESS

TEST MANAGER Test Info Select Project View/Update Test Case View/Update DATAPOOL View/Update Expected Results View Results Open Automation Script

TEST MANAGER Test Execution Insert Test Cases to scenario Insert Iterations number Run Test