Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Test automation


Published on

  • Be the first to comment

  • Be the first to like this

Test automation

  1. 1. Successful Methods in Test Automation 12/29/10 For more QTP Scripts,
  2. 2. Content … <ul><li>Why Automation ? </li></ul><ul><li>Manual vs. Automated </li></ul><ul><li>Automation Methodologies – Best Method </li></ul><ul><li>Why QTP? – Advantages of QTP </li></ul><ul><li>Architecture Setup </li></ul><ul><li>Test Automation Architecture </li></ul><ul><li>Parallel Run – Manual vs. Automation </li></ul><ul><li>Prerequisite - Resource selection </li></ul><ul><li>Designing – Coding – Testing </li></ul><ul><li>Setup Requirements for Automation Runs </li></ul><ul><li>Maintenance/Support </li></ul>12/29/10 For more QTP Scripts,
  3. 3. Why Automation ? - Benefits <ul><li>Benefits to Automation include increased software quality, improved time to market, repeatable test procedures, and reduced testing costs. </li></ul><ul><li>REDUCED TESTING TIME </li></ul><ul><li>IMPROVED TESTING PRODUCTIVITY </li></ul><ul><li>IMPROVED PRODUCT QUALITY </li></ul><ul><li>REDUCED QA COSTS </li></ul><ul><li>CONSISTENT TEST PROCEDURES </li></ul><ul><li>CAN SCHEDULE TEST RUNS </li></ul>12/29/10 For more QTP Scripts,
  4. 4. Manual vs. Automated <ul><li>Manual Execution </li></ul><ul><li>More No. of resources required </li></ul><ul><li>Slow,takes time to retest incase </li></ul><ul><li>of testing in multiple environments </li></ul><ul><li>There is a chance of overlook </li></ul><ul><li>Automation </li></ul><ul><li>Less No. of resources required </li></ul><ul><li>Fast, Accurate and Reliable </li></ul><ul><li>Improves testing productivity </li></ul><ul><li>Easy to Learn & Maintain </li></ul>12/29/10 For more QTP Scripts,
  5. 5. Automation Methodologies <ul><li>Methodologies that have been found to be effective for automating functional or system testing for most business applications are broadly categorized as: </li></ul><ul><li>1. The &quot;Functional Decomposition&quot; Method: </li></ul><ul><ul><li>(Mostly followed for Desktop applications) </li></ul></ul><ul><ul><li>To reduce all test cases to their most fundamental tasks, and write User-Defined Functions, Business Function Scripts, and &quot;Sub-routine&quot; or &quot;Utility“ Scripts which perform these tasks independently of one another </li></ul></ul><ul><li>2. The &quot;Key-Word Driven&quot; or &quot;Test Plan Driven&quot; Method: (Mostly followed for Web based applications) In this method, the entire process is data-driven, including functionality. This method uses the actual Test Case document developed by the tester using a spreadsheet containing special &quot;Key-Words&quot;.  </li></ul>12/29/10 For more QTP Scripts,
  6. 6. Why QTP ? <ul><ul><ul><li>Allows even novice testers to be productive in minutes. </li></ul></ul></ul><ul><ul><ul><li>Create a test script by simply pressing a Record button and using an application to perform a typical business process. </li></ul></ul></ul><ul><ul><ul><li>Each step in the business process is automated documented with a plain-English sentence and screen shot. </li></ul></ul></ul><ul><ul><ul><li>Can easily modify, remove, or rearrange test steps. </li></ul></ul></ul><ul><ul><ul><li>By capturing, verifying and replaying user interactions automatically, </li></ul></ul></ul><ul><ul><ul><li>Identifies defects and helps ensure that business processes deliver the expected results and remain reliable throughout the lifecycle. </li></ul></ul></ul><ul><ul><ul><li>Available for browser-based and Java-based applications and ERP/CRM solutions. </li></ul></ul></ul>12/29/10 For more QTP Scripts,
  7. 7. Why QTP ? Contd… <ul><ul><ul><li>Report displays all aspects of the test run: </li></ul></ul></ul><ul><ul><ul><li>:: a high-level results overview, </li></ul></ul></ul><ul><ul><ul><li>:: an expandable Tree View of the test script </li></ul></ul></ul><ul><ul><ul><li>Specifying exactly :: </li></ul></ul></ul><ul><ul><ul><li>Where application failures occurred </li></ul></ul></ul><ul><ul><ul><li>The test data used </li></ul></ul></ul><ul><ul><ul><li>Application screen shots for every step that highlight any discrepancies </li></ul></ul></ul><ul><ul><ul><li>Detailed explanations of each checkpoint pass and failure </li></ul></ul></ul><ul><ul><ul><li>Can share reports across an entire QA and development team </li></ul></ul></ul>12/29/10 For more QTP Scripts,
  8. 8. Why QTP ? Contd… <ul><ul><ul><li>Supports functional testing of all popular environments, including :: </li></ul></ul></ul><ul><ul><ul><li>Windows, </li></ul></ul></ul><ul><ul><ul><li>Web, </li></ul></ul></ul><ul><ul><ul><li>.Net, </li></ul></ul></ul><ul><ul><ul><li>Visual Basic, </li></ul></ul></ul><ul><ul><ul><li>ActiveX, </li></ul></ul></ul><ul><ul><ul><li>Java, </li></ul></ul></ul><ul><ul><ul><li>SAP, </li></ul></ul></ul><ul><ul><ul><li>Siebel, </li></ul></ul></ul><ul><ul><ul><li>Oracle, </li></ul></ul></ul><ul><ul><ul><li>PeopleSoft, </li></ul></ul></ul><ul><ul><ul><li>terminal emulators </li></ul></ul></ul>12/29/10 For more QTP Scripts,
  9. 9. Architecture Setup It takes at least 3 – 6 months to setup an architecture, which includes the following phases. 1. Installation: This includes hardware, software and network setup . 2 . Analysis: This includes better understanding/definition of the base system covering all the Functional Area to be automated. 3. Pilot Project: This covers the scripting of the base functional area based on the analysis/defined architecture.After Completion of pilot,a Parallel Run (Manual Vs. Automation) is required. 4. Architecture Acceptance: This includes the Test Run of the pilot project on the defined architecture to continue further automation of functional areas over the base project. 12/29/10 For more QTP Scripts,
  10. 10. Test Automation Architecture 12/29/10 For more QTP Scripts, Test Environments
  11. 11. Parallel Run – Manual vs. Automation Parallel Execution: After the completion of Pilot Project, a parallel run can be done between Manual and Automation for at least 2 Releases to see the results Manual - 300 People Hours Automation - 30 Machine Hours 12/29/10 For more QTP Scripts, 1 2 3 … 50 n
  12. 12. Prerequisite - Resource selection <ul><li>Following skills are required for the Automation Scripting/Projects. </li></ul><ul><li>Testers having exposure to coding </li></ul><ul><li>Good Analytical skills </li></ul><ul><li>Good Logic / Aptitude </li></ul><ul><li>Better understanding of SDLC and Testing Life Cycle </li></ul><ul><li>Problem Identification / Solving skills </li></ul><ul><li>Developers having testing knowledge </li></ul><ul><li>Attitude to learn </li></ul><ul><li>Exposure to other Automation Tools like Win Runner, Rational etc… </li></ul>12/29/10 For more QTP Scripts,
  13. 13. Designing – Coding – Testing <ul><ul><li>Functional Area </li></ul></ul><ul><ul><li>Analysis/Requirement gathering/ </li></ul></ul><ul><ul><li>Logical Designing </li></ul></ul><ul><li>Deployment/ Functional </li></ul><ul><li>Maintenance/ Area </li></ul><ul><li>PR/CR Requests Scripting </li></ul><ul><li> Testing / UAT / </li></ul><ul><li> Bug Fixes </li></ul>12/29/10 For more QTP Scripts,
  14. 14. Setup Requirements for Automation Runs <ul><li>Following are the base requirements for run Setup: </li></ul><ul><li>Dedicated machines for test runs </li></ul><ul><li>Stable Test Environment </li></ul><ul><li>Dedicated resources having exposure to QTP and Datasheets </li></ul><ul><li>Resources having Automated Functional Area knowledge </li></ul><ul><li>Latest Merged Automated test scripts </li></ul><ul><li>Quality Centre Setup – For Scheduling Automation Runs </li></ul><ul><li>Defect Tracking tool to log PR s / CR s </li></ul><ul><li>Updated test cases of the respective Functional areas </li></ul>12/29/10 For more QTP Scripts,
  15. 15. Maintenance/Support <ul><li>Following points should be taken into consideration for proper maintenance and support : </li></ul><ul><li>Dedicated Maintenance / Support Team </li></ul><ul><li>Tracking of all the changes in the coming releases </li></ul><ul><li>Team should respond to the PR’s on Priority </li></ul><ul><li>Team should update the script for all the PR’s / CR’s as per the </li></ul><ul><li>coming release </li></ul><ul><li>Separate QTP setup for maintenance / support team </li></ul><ul><li>Version Control for test scripts, datasheets & library files </li></ul><ul><li>Merging of updated scripts should be in accordance with the </li></ul><ul><li>standards </li></ul>12/29/10 For more QTP Scripts,
  16. 16. Thank You ! 12/29/10 For more QTP Scripts,