Automation testing IBM RFT - Rational Functional Tester

  • View

  • Download

Embed Size (px)

Text of Automation testing IBM RFT - Rational Functional Tester

  • 1.- Automation Testing - Rational Functional Tester

2. Understanding Automation Testing Web Automation Challenges Road map to Success & best Practice IBM Rational Functional Tester Automation Framework Confidential Agenda 3. What? Test automation is the use of software to control the execution of tests. Commonly, test automation involves automating a manual process already in place that uses a formalized testing process. Why? Reduce the impact on the bottom line in Regression Testing. Increase the flexibility of time and resource. Fast and Accuracy. When? Frequency build and regression testing on demand. Mission critical business & long term maintenance To avoid Human errors. To check real time performance of the application. GUI Frozen Confidential Automation Testing What? -Why? -When? 4. Test Automation is simple, that every tester can do it This myth is promoted by the tool sales people. They are trying to promote the following test automation process: Record the script Enhance the script by adding functions and data driving Run the scripts Report results Under the influence of this myth the QA manager can proudly report: All our testers are developing test automation. Confidential Myth # 1 5. Test automation is a software development task Automation should be designed, developed and tested You need to have some kind of a programming background to implement test automation. Test Automation is not as complex as C++ or C# or Java or VB development. Test automation standards should be developed Automated test components are assets that should be treated like application source code Confidential Myth #1 - The Reality 6. Commercial test tools are expensive Under the influence of this myth some companies, especially the small ones: Try to develop their own test automation tools Use scripting languages like Perl and Ruby Use shareware test tools Do not consider test automation at all Confidential Myth #2 7. Commercial tools are cheap Per seat license for the most expensive automation tool is $8K. This tool will be used for 5 years. Maintenance/Support fees are 20% of tool cost or $1,800 per year. The cost of this tool is $8K/5+$1,800 = $3,100 per year. The automation developer cost with overhead is $100K per year. The cost of this tool is just 3% of the person who uses it, but productivity gain can be very significant. Confidential Myth #2 - The Reality 8. Customer support. Many of the open source tools come and go with little to no support . Most commercial tools are constantly being updated as technologies change. Most commercial tools usually have more functionality (IBM RFT & QTP can test various GUI applications: Web, .Net, Java, VB, C/C++, Power Builder, etc. vs. WATIR Web only) Commercial tools usually have a large community of users, which translates into better availability of qualified resources Commercial tools require less advanced programming More test automation frameworks are available for commercial tools Commercial tools are integrated with Test Management tools which makes reporting and execution much simpler. Confidential Commercial Benefits 9. Over 300 Test Tools are available in market ( Load/Performance tools 54 Web Functional/Regression 60 Java Test tools 48 Other Web tools 76 Confidential Commercial Tools 10. Confidential Dice search results across US (30 days, Jan 2010) 11. Confidential Demand Per Tool 12. Excerpt from IDC Report:- Worldwide Automated Software Quality 2007-2011 Forecast and 2006 Vendor Shares Confidential Automation is Future ! 13. ROI value IS NOT the value of Automation vs. Cost of executing these tests manually Automation ROI value IS the benefit of this type of testing, and it can be: Reducing Time to Market. Increased Test Efficiency (Productivity) Increased Test Effectiveness. Confidential Classic ROI Calculation 14. Can get a greater market share Makes people available to work on other projects Higher margins, if no competitive products are currently available Reduce time to market Confidential ROI helps to .. 15. More testing gets done faster, increasing the odds of finding defects. Defects found early have better chances of being fixed. Manual Testers can concentrate on clever ways to finding defects, instead of typing test inputs and verify output. Confidential ROI - Productivity and effectiveness 16. Each project requires different types of automation - there is often no easy formula available to calculate ROI Performing ROI calculation can help to determine upfront what type of automation, what level of skills, what tools will be required. Confidential ROI Summary 17. Is Automation is expensive ? Yes of course ! Its expensive and time consuming effort at initial stage. Confidential ROI 18. Functionality testing GUI. Business validation. Data Base. Performance Testing Stress Test Load Test Volume TestConfidential Automation Capabilities 19. Are you thinking of 100% Automation ? Impossible ..Stop Dreaming. Certainly you have areas like performance testing, regression testing, load/stress testing where you can have chance of reaching near to 100% automation. Areas like User interface, documentation, installation, compatibility and recovery where testing must be done manually. Will your automation suite be having long lifetime? Confidential General qualms 20. Is Tool Selection more Important ? Be sure to have skilled staff before deciding to automate your testing work. Make sure that tool is a best fit to your requirements Find out the limitations of the tool that is best match with your requirements Confidential General qualms 21. Why web application is different in Test Automation Perspective ? Many web based commercial system like B-C, B-B & C-C Catering to large number of end user. People with varying background & technical skills may use the application. Network thread (Security , Connection speed (Broad band , dial-up etc.. )) Numerous application usage. Confidential Web Automation 22. Rule 1: Get familiar with Business. Rule 2: Get familiar with Tool. Rule 3: Have at least one real programmer in your team. Rule 4: Set some standards. * Naming standards * Coding standards * Environment standards * Procedure for error and defect tracking system * Documentation standards.Confidential 8 Rules for Successful Automation 23. System Requirements Processor : Pentium- 4 , 1.4 + GHz (HT) RAM : Min 1 GB Recommended 2GBConfidential IBM Rational Functional Tester IBM Rational Functional Tester for Java 24. Introduction to Functional Tester Working with a Functional Test Project Setting up the Test Environment Getting Started.. 25. Rational Functional Test is an object-oriented automated testing tool that tests Java, HTML, VB.NET, and Windows applications, and lets you record reliable and robust scripts that can be played back to validate new builds of a test application. Functional Test runs on Windows 2000, Windows XP, and Linux platforms Confidential Introduction to Functional Tester 26. Functional Test is available in two integrated development environments and two scripting languages. Functional Test, Java Scripting uses the Java language and the IBM Rational Software Development Platform. Functional Test, VB.NET Scripting uses the VB.NET language and the Microsoft Visual Studio .NET development environment. Confidential Introduction to Functional Tester (Cont..) 27. With the object-oriented recording technology of Functional Tester, you can generate scripts by running and using the application-under-test. Functional Tester scripts are implemented as Java programs. Functional Tester is integrated with IBM Rational Test Manager, which enables you to record and play back a Functional Tester script from Test Manager and make use of Test Manager test logs. Alternatively, Functional Tester can be used as a standalone product, using HTML or text logs to review test results.Confidential Functional Tester Features 28. Confidential Script Recording and Playback Process 29. Confidential Starting Functional Tester Click Start > Programs > IBM Rational Software Development Platform > Functional Tester V6.1 > Java Scripting 30. The workbench is the desktop development environment that lets you work with multiple tools seamlessly. The workbench contains one or more perspectives. A perspective provides a set of functionality for working with specific tasks or types of resources. You switch between different tasks and resources by selecting your perspective. Perspectives define the initial workspace configuration and layout.Confidential Perspectives 31. Confidential Perspectives (Cont..) 32. Switch from one perspective to another to carry out a different task Perspectives can be opened In the same (existing) window In a new window In the same window, replacing the current perspective Confidential Perspectives (Cont..) 33. The perspectives can be opened in the same window or in a new workbench window. For example, if you want to see Functional Test Debug at the same time as the Java editor, you can open the Functional Test Debug perspective in a separate window. If you always want to open a perspective in its own window, you can set it up as a user preference. To do this, click Window > Preferences > Workbench > Perspectives and then, under Open a newConfidential Perspectives (Cont..) 34. To Open a Perspective: From the Functional Test perspective, click Window > Open Perspective or click the Open a perspective button. Click one of the listed perspectives or click Other to display a list of perspectives .(The Functional Test Debug and Java perspectives are listed by default, but this menu changes depending on which perspectives are open.)Confidential Perspective (Cont..) 35. The Functional Test Projects view lists test assets for each p


View more >