Manual Software Testing V/S Automated Testing
Manual Software Testing V/S Automated Testing
Manual Software Testing V/S Automated Testing
In an Organization, a Project or Product Process is having Multiple Stages of Development and Multiple stages of Testing. A Separate Testing Team is involved in Software Testing Stage to Validate Corresponding Software with respect to Customer Requirements ( Functional Testing ) and with respect to Customer Expectations ( Non - Functional Testing ) During this Software Testing, Testers are Testing Software Functionalities and Characteristics by following Black Box Testing Techniques and valid Matrices in Manual style or in Automation style.
Manual Testing
Automated Testing
SUT
Test Case
Tester
Test Case
Tester
Test Automation Converting Case in to Program / Script. Automated Testing Converted Program Run on Project to Detect Defects. In General, Tester can write Test Cases in English by following Black Box Testing Techniques in IEEE 829 Format in MS-EXCEL or in a Management Tool like QC. Those cases in English will be converted to Automated Test Scripts in Computer Languages by using Testing Tools.
Page | 1 MIND Q - Nageshwar Rao's Software Testing Tools - Batch 180 ( December 2011 - Feb 2012 )
Double 'V' Model Verification BRS Validation Acceptance Testing Automation Fitness, Expectetc
SRS
Software Testing
HLD
Integration Testing
LLD's
Unit Testing
Coding Tester Job Study SRS and Conduct Software Testing using Available Tools. Domain Knowledge A Software Tester can study SRS to understand Project Requirements Example Banking, Insurance, Health Care, Tele Communications, . . . Testing Knowledge Software Tester can conduct Different Types of Tests on Software to Detect Defects. Example Functional, Non Functional Programming Knowledge During Software Testing, Testers can use some Testing Tools to finish Testing as early as possible. Example Front End Testing, Back End Testing Page | 2 MIND Q - Nageshwar Rao's Software Testing Tools - Batch 180 ( December 2011 - Feb 2012 )
Software Tester needs Programming Knowledge for Automation to integrate with corresponding SUT Front End Screens and corresponding SUT Backend Database.
SUT
Database Backend
Database Test Automation F.T.A. : Frontend Test Automation Selenium Tool F.T.A. Core Java SQL Screens Frontend Database Backend SUT
Database Test Automation Note Most of the Companies use Vb script for Front End Automation than Jscript. Jscript is different from Java Script. Jscript : Developed by Microsoft Java Script : Developed by Sun Systems Selenium : Tests only Web based Projects ( HTML ) QTP : Tests any kind of Projects ( ERP, Visual Basic, . . . )
Page | 3 MIND Q - Nageshwar Rao's Software Testing Tools - Batch 180 ( December 2011 - Feb 2012 )
Testing Tools are classified in to 4 Generations 1st Win Runner SQA Robot Silk Test . . . Licensed Inbuilt Languages TSL 2nd QTP Load Runner . . . . Licensed Public Languages QTP - Vb Script Load Runner - C 3rd Selenium Jmeter . . . . No License Required Open Source Files Support Development Languages Selenium - Core Java 4th PERL Python Ruby Rexx . . Programming Languages
1st Generation Tools 1st Generation Tools are Commercial ( Licensed ) and support inbuilt Languages only. Example Win Runner is licensed Tool and support TSL ( Test Script Language )
2nd Generation Tools 2nd Generation Tools are Commercial. But, they support Development Languages to prepare Test Scripts. Example QTP is licensed and support Vb Script Language.
Page | 4 MIND Q - Nageshwar Rao's Software Testing Tools - Batch 180 ( December 2011 - Feb 2012 )
3rd Generation Tools 3rd Generation Tools are Open Source ( Free ) and they can support Development Languages. Example Selenium is Open Source and Supports Core Java.
4th Generation Tools 4th Generation Tools are not Tools. But, they are Direct Programming Languages like PERL, Python, Ruby, Rexx, . . .
NOTE * Every Automated Tester is also a Manual Tester. But, Every Manual Tester is not an Automated Tester ( Programming Knowledge Required ) * 100 Percent Automation in Testing is of no need and is almost impossible. * In Every Stage of Testing, Automation is Possible i.e. Automation Facilities are Available. * In Manual Tests, there are No Limitations. If Skills are available and Resources ( Facilities ) are provided, we can go and test. * In a Company, Manual Tests are Compulsory. But, Automated Tests are Optional. * To Avoid Repetition in Tests, Automation is Preferred.
Page | 5 MIND Q - Nageshwar Rao's Software Testing Tools - Batch 180 ( December 2011 - Feb 2012 )
Need for Automation in Software Testing In Software Testing Automation, Testing Teams are following the Following Conditions or Limitations Sanity Testing Functional Testing Performance Testing Other Non Functional Testing Manual Automation ( Load Runner ) Manual Real Testing Manual Automation ( Load Runner ) Manual Regression Testing Automation ( QTP / Selenium ) Automation ( Load Runner ) Manual Final Regression Testing Automation ( QTP / Selenium ) Automation ( Load Runner ) Manual
In Functional Testing, Automation was needed at Regression Testing and Final Regression Testing to Finish Repetition of Tests as early as possible. In Performance Testing, Automation was needed at Every Level because Manually Performance Testing is Costly and Complex to Conduct. To Automate Data volume Testing and Inter system Testing / SOA Testing, we can use Functional Testing Tools (QTP). The remaining Non Functional Testing Topics like Compatibility, Configuration, Usability, Multi-languity, Installation, Security and Parallel Testing are conducted by Testers Manually due to Lack of well-known corresponding Testing Tools in Market. ( If Reliable Tools available, then, we can think of Automation ) HP QTP (11.0) * QTP stands for Quick Test Professional. * It is a Functional Regression Testing Tool. * 11.0 is recent version released by HP ( Beta Version - Nov 2010 - January 2011 ) * QTP is a Standalone Software and not a Network Software, * QTP do not run at Server ( Shareable Network ). It runs at Individual Client Systems. * All Standalone Pc's and Laptops are eligible to load QTP. * First Version of QTP is 5.5 * Original Name of QTP used to be AQT ( Astra Quick Test ) up to its 5.0 Version. * QTP cannot be installed in Unix or Linux Operating Systems. * QTP fully Supports Functional Testing and Partially Supports Non Functional Testing.
Page | 6 MIND Q - Nageshwar Rao's Software Testing Tools - Batch 180 ( December 2011 - Feb 2012 )
Mercury Interactive Win Runner . . Strength of AQT + Strength of Win Runner QTP 5.5 . . Take Over by HP
* QTP will be installed in Windows Client or in Windows Server Based Computers and working as Standalone ( Not Sharable to others ) ( Not shareable to Clients Computers even if it is loaded in Server ) * QTP can Automate Functional Test cases on Windows Based and Web Based SUT, QTP doesnt support Command Based SUT Automation. * QTP supports 2 Types of GUI ( Graphical User Interface ) projects Running in Internet Web based Project Running in Windows Windows based Project
* QTP does not support Command based SUT Automation ( Command Line Interface )
Page | 7 MIND Q - Nageshwar Rao's Software Testing Tools - Batch 180 ( December 2011 - Feb 2012 )
* QTP can Automate Functional Test Cases on Windows based and Web based SUT, when that SUT Screens ( Front End ) developed in JAVA Dot Net Vb SAP PeopleSoft Oracle Apps HTML(Web) Power builder Delphi Stingray Visual Age Small Talk Siebel Standard Windows ( Not an Operating System - It is a Technology to Develop Software's ) Terminal Emulators ( C, C++, Mainframes ) Silver Light ( New Support in 11.0 ) * QTP can Automate Functional Test Cases on Web Based SUT, when that Site Pages are developed in HTML along with Flex, but QTP needs Flex Plug-in Installation provided by Adobe Corporation. * To Automate Functional Test Cases on Mobile Based SUT, we can Integrate QTP 11.0 with Webneir of Perfecto Soft Company.
Page | 8 MIND Q - Nageshwar Rao's Software Testing Tools - Batch 180 ( December 2011 - Feb 2012 )
* QTP can support Functional Test Cases Automation on SUT Database developed in any Technology like Oracle Toad Tivoli SQL MS Access Sybase FoxPro My SQL DB2 Terradata,. . e t c. * QTP have Web-Services Add-in for SOA Test Automation. * Using QTP, we can Automate Data Volume Testing also to find capacity of SUT Database.
NOTE * Once the Client Requirement is Changing, Developer is going to use Advanced Technology. * Once Developer is going to use Advanced Technology, Testers are going to use Advanced Technology * C, C++, Cobol able to Test using QTP, but with provided Dummy Screens, Drivers and Stuff. * Simulation = Virtuality * Oracle is different from Oracle Apps. Oracle is useful for Front End. Oracle Apps is useful for Backend. * My SQL is Open Source. It can be downloaded from Apache website and used for free. * QTP is not just a Testing Tool. It is also a Technology. Complete QTP = QTP Tool ( Editor / Screen ) + QTP Script ( Language )
Page | 9 MIND Q - Nageshwar Rao's Software Testing Tools - Batch 180 ( December 2011 - Feb 2012 )
Case Study 1 Frontend Functional Test Automation Windows based SUT ( 2 Tier )
Database
Vb script / Jscript QTP Script Vb, Dot net, Java, SAP, Oracle Apps, HTML, People Soft, . . . e.t.c.
pages
Page | 10 MIND Q - Nageshwar Rao's Software Testing Tools - Batch 180 ( December 2011 - Feb 2012 )
Case Study 2 Backend Functional Test Automation Windows based SUT ( 2 Tier )
Screens QTP Tool Vbscript / Jscript QTP Script Dot net Factory My SQL, Oracle, SQL Server, Sybase, . . . e.t.c.
Database
pages
The above diagram is emulating Back-end Functional Test Automation including Data volume Test Automation also. NOTE Testing
Functional
Non Functional
Frontend
Backend
* Database developed in any Technology, QTP is ready to Test it effectively. * Tester needs to learn Vbscript and SQL Commands for Automated Testing.
Page | 11 MIND Q - Nageshwar Rao's Software Testing Tools - Batch 180 ( December 2011 - Feb 2012 )