Continue # Infosys Whitepaper 
/ 8  

---

 Implementing Hybrid  Framework with  Selenium •  Store the test data (any user input data) in an Excel file.<|endoftext|>•  Store the environment related information (for example, QA, UAT, Regression) in a  property file.<|endoftext|>•  Store various objects in the application on which user action needs to be taken in object  repository files.<|endoftext|>•  Test suite contains the logic to verify acceptance criteria mentioned in the requirement.<|endoftext|>•  Execute the script on various browsers as per the need.<|endoftext|>•  Generate the reports capturing screenshots and pass/fail results. To get advanced  reports in Selenium use any testing framework such as TestNG, JUnit.<|endoftext|>Now let us see how to implement  a hybrid framework with  Selenium as an automation  tool. The key points in the  implementation are: Test Data (Excel) Data Layer (Input test data,  environment)  Property  File Object  A Object  B Object  C Object  Repository Test  Scripts Test  Suite ANT  Builder Execute Reporting Module [Captured Screenshots, XML Based Logs and HTML  Based Reports] Application under Test (AUT) External Document © 2018 Infosys Limited 

---

  Page: 7 / 8  

---

 Implementing Hybrid  Framework with QTP/ UFT •  Store the test data (any user input data) in an Excel file.<|endoftext|>•  Create a run manager sheet to drive the test execution.  •  Store the environment-related information in property file.  •  Store the objects in the application on which user actions are taken in object  repository files.  •  Divide the test cases into modular functions, keeping common functions separately  to be used across projects.  •  Include main script common functions, object repository and test data. Generate  different types of reports as per the business requirements.<|endoftext|>Let us discuss how to implement  a hybrid framework with QTP/ UFT as an automation tool. The  key points in the implementation  are: Test Data (Excel) Data Layer Environment  data App 1 App 2 App 3 Object  Repository Reusable  functions Test  Suite Test  Suite Execute Execution  Summary Application under Test (AUT) Reporting Module Test Script  Results Error  Log External Document © 2018 Infosys Limited 

---

  Page: 8 / 8  

---

 Executing Proof of Concept  for the Selected Tool The last phase of tool evaluation is proof  of concept (PoC). The tool selected may  satisfy your criteria conceptually, but it  is advisable to test the tool using a few  scenarios. Almost every tool vendor  provides an evaluation version of their tool  for a limited time period. The following  steps need to be considered during the  PoC: •  Choose a few scenarios in such a way  that they cover different objects and  controls in the application.<|endoftext|>•  Select the tool(s) based on a  comparative study.<|endoftext|>•  Automate the chosen scenarios using  the selected tool(s).<|endoftext|>•  Generate and analyze various reports.<|endoftext|>•  Analyze the integration of the tool with  other tools such as test management  tool available, for example, QC  (Quick Center) and with continuous  integration tools such as Jenkins.<|endoftext|>While evaluating multiple tools, generate  a score-card based on various parameters  such as ease of scripting, integration,  usage, reports generated and chose the  tool with the maximum score. When the  POC is completed, the team can be more  confident about successfully automating  the application using the selected tool.<|endoftext|>Conclusion The process of automation framework design and development  requires detailed planning and effort.  To achieve the desired  benefits, the framework must be accurately designed and  developed. Such a framework can then be used across projects  in an organization and provides substantial ROI. When choosing  an automation framework, it is crucial to ensure that it can easily  accommodate the various automation testing technologies and  changes in the system under test.<|endoftext|>One of the key factors contributing to the accomplishment of  any test automation project is identifying the right automation  tool. A detailed analysis in terms of ease of use, reporting  and integration with various tools must be performed before  selecting a tool. Though such selection processes call for focused  effort and time, this investment is worth making because of the  great impact it has on the success of the automation project.<|endoftext|>About the 
Author Harsh Bajaj is a Technical Test Lead with Infosys Independent Validation Services Team.  She has led various test automation projects in the telecom domain. She is proficient  in various test management and automation tools.  About the Reviewer Gautham Halambi is a Project Manager with Infosys and has more than 9 years of  experience. He has worked on multiple telecom testing projects and has led and  managed large manual and automation testing teams.<|endoftext|>References www.seleniumhq.org www.watir.com,  http://www.gebish.org/ http://www.automationrepository.com/ http://en.wikipedia.org/wiki/Keyword-driven_testing © 2018 Infosys Limited, Bengaluru, India. All Rights Reserved. Infosys believes the information in this document is accurate as of its publication date; such information is subject to change without notice. Infosys  acknowledges the proprietary rights of other companies to the trademarks, product names and such other intellectual property rights mentioned in this document. Except as expressly permitted, neither this  documentation nor any part of it may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, printing, photocopying, recording or otherwise, without the  prior permission of Infosys Limited and/ or any named intellectual property rights holders under this document.  For more information, contact askus@infosys.com Infosys.com | NYSE: INFY Stay Connected   


***


  