1 Sample Test Automation Tool Rational offers the most complete lifecycle toolset (including testing) of these vendors for the windows platform. When it comes to Object Oriented development they are the acknowledged leaders with most of the leading OO experts working for them. Some of their products are worldwide leaders e.g. Rational Robot, Rational Rose, Clear case, RequistePro, etc.Their Unified Process is a very good development model that I have been involved with which allows mapping of requirements to use cases, test cases and a whole set of tools to support the process. 1 Rational Suite of tools Rational RequisitePro is a requirements management tool that helps project teams control the development process. RequisitePro organizes your requirements by linking Microsoft Word to a requirements repository and providing traceability and change management throughout the project lifecycle. A baseline version of RequisitePro is included with Rational Test Manager. When you define a test requirement in RequisitePro, you can access it in Test Manager. Rational Clear Quest is a change-request management tool that tracks and manages defects and change requests throughout the development process. With Clear Quest, you can manage every type of change activity associated with software development, including enhancement requests, defect reports, and documentation modifications. Rational Purify is a comprehensive C/C+ + run-time error checking tool that automatically pinpoints run-time errors and memory leaks in all components of an application, including third-party libraries, ensuring that code is reliable Rational Quantify is an advanced performance profiler that provides application performance analysis, enabling developers to quickly find, prioritize and eliminate performance bottlenecks within an application. Rational Pure Coverage is a customizable code coverage analysis tool that provides detailed application analysis and ensures that all code has been exercised, preventing untested code from reaching the end-user. Rational Suite Performance Studio is a sophisticated tool for automating performance tests on client/server systems. A client/server system includes client applications accessing a database or application server, and browsers accessing a Web server. Performance Studio includes Rational Robot and Rational Load Test. Use Robot to record client/server conversations and store them in scripts. Use Load Test to schedule and play back the scripts. Rational Robot. Facilitates functional and performance testing by automating record and playback of test scripts. Allows you to write, organize, and run tests, and to capture and analyze the results. Rational Test Factory. Automates testing by combining automatic test generation with source-code coverage analysis. Tests an entire application, including all GUI features and all lines of source code. During playback, Rational Load Test can emulate hundreds, even thousands, of users placing heavy loads and stress on your database and Web servers. Rational Test categorizes test information within a repository by project. You can use the Rational Administrator to create and manage projects. The tools that are to discussed here are Rational Administrator Rational Robot Rational Test Manager 2 Rational Administrator What is a Rational Project? A Rational project is a logical collection of databases and data stores that associates the data you use when working with Rational Suite. A Rational project is associated with one Rational Test data store, one RequisitePro database, one Clear Quest databases, and multiple Rose models and RequisitePro projects, and optionally places them under configuration management. Rational administrator is used to create and manage rational repositories, users and groups and manage security privileges. How to create a new project? Open the Rational administrator and go to File->New Project. In the above window opened enter the details like Project name and location. Click Next. In the corresponding window displayed, enter the Password if you want to protect the project with password, which is required to connect to, configure or delete the project. Click Finish. In the configure project window displayed click the Create button. To manage the Requirements assets connect to Requisite Pro, to manage test assets create associated test data store and for defect management connect to Clear quest database. Once the Create button in the Configure project window is chosen, the below seen Create Test Data store window will be displayed. Accept the default path and click OK button. Once the below window is displayed it is confirmed that the Test datastore is successfully created and click OK to close the window. Click OK in the configure project window and now your first Rational project is ready to play with…. Rational Administrator will display your “TestProject” details as below: 3 Rational Robot Rational Robot to develop three kinds of scripts: GUI scripts for functional testing and VU and VB scripts for performance testing. Robot can be used to: • Perform full functional testing. Record and play back scripts that navigate through your application and test the state of objects through verification points. • Perform full performance testing. Use Robot and TestManager together to record and play back scripts that help you determine whether a multi-client system is performing within user-defined standards under varying loads. • Create and edit scripts using the SQABasic, VB, and VU scripting environments. The Robot editor provides color-coded commands with keyword Help for powerful integrated programming during script development. • Test applications developed with IDEs such as Visual Basic, Oracle Forms, PowerBuilder, HTML, and Java. Test objects even if they are not visible in the application's interface. • Collect diagnostic information about an application during script playback. Robot is integrated with Rational Purify, Quantify, and PureCoverage. You can play back scripts under a diagnostic tool and see the results in the log. The Object-Oriented Recording technology in Robot lets you generate scripts quickly by simply running and using the application-under-test. Robot uses Object-Oriented Recording to identify objects by their internal object names, not by screen coordinates. If objects change locations or their text changes, Robot still finds them on playback. The Object Testing technology in Robot lets you test any object in the application-under-test, including the object's properties and data. You can test standard Windows objects and IDE-specific objects, whether they are visible in the interface or hidden. 4 Robot login window Once logged you will see the robot window. Go to File-> New->Script In the above screen displayed enter the name of the script say “First Script” by which the script is referred to from now on and any description (Not mandatory).The type of the script is GUI for functional testing and VU for performance testing. 5 Rational Robot main window-GUI script 2 The GUI Script top pane) window displays GUI scripts that you are currently recording, editing, or debugging. It has two panes: • Asset pane (left) – Lists the names of all verification points and low-level scripts for this script. • Script pane (right) – Displays the script. The Output window bottom pane) has two tabs: • Build – Displays compilation results for all scripts compiled in the last operation. Line numbers are enclosed in parentheses to indicate lines in the script with warnings and errors. • Console – Displays messages that you send with the SQAConsoleWrite command. Also displays certain system messages from Robot. To display the Output window: Click View ® Output. How to record a play back script? To record a script just go to Record->Insert at cursor Then perform the navigation in the application to be tested and once recording is done stop the recording. Record-> Stop 6 Record and Playback options Go to Tools-> GUI Record options the below window will be displayed. In this window we can set general options like identification of lists, menus ,recording think time in General tab: Web browser tab: Mention the browser type IE or Netscape… Robot Window: During recording how the robot should be displayed and hotkeys details… Object Recognition Order: the order in which the recording is to happen . For ex: Select a preference in the Object order preference list. If you will be testing C++ applications, change the object order preference to C++ Recognition Order. 1 Playback options Go to Tools-> Playback options to set the options needed while running the script. This will help you to handle unexpected window during playback, error recovery, mention the time out period, to manage log and log data. 7 Verification points A verification point is a point in a script that you create to confirm the state of an object across builds of the application-under-test. During recording, the verification point captures object information (based on the type of verification point) and stores it in a baseline data file. The information in this file becomes the baseline of the expected state of the object during subsequent builds. When you play back the script against a new build, Robot retrieves the information in the baseline file for each verification point and compares it to the state of the object in the new build. If the captured object does not match the baseline, Robot creates an actual data file. The information in this file shows the actual state of the object in the build. After playback, the results of each verification point appear in the log in Test Manager. If a verification point fails (the baseline and actual data do not match), you can select the verification point in the log and click View ® Verification Point to open the appropriate Comparator. The Comparator displays the baseline and actual files so that you can compare them. A verification point is stored in the project and is always associated with a script. When you create a verification point, its name appears in the Asset (left) pane of the Script window. The verification point script command, which always begins with Result =, appears in the Script (right) pane. Because verification points are assets of a script, if you delete a script, Robot also deletes all of its associated verification points. You can easily copy verification points to other scripts if you want to reuse them. 1 List of Verification Points The following table summarizes each Robot verification point. Type Description Alphanumeric Captures and compares alphabetic or numeric values. Clipboard Captures and compares alphanumeric data that has been copied to the Clipboard. File Comparison Compares the contents of two files. File Existence Checks for the existence of a specified file Menu Captures and compares the text, accelerator keys, and state of menus. Captures up to five levels of sub-menus. Module Existence Checks whether a specified module is loaded into a specified context (process), or is loaded anywhere in memory. Object Data Captures and compares the data in objects. Object Properties Captures and compares the properties of objects. Region Image Captures and compares a region of the screen (as a bitmap). Web Site Compare Captures a baseline of a Web site and compares it to the Web site at another point in time. Web Site Scan Checks the content of a Web site with every revision and ensures that changes have not resulted in defects. Window Existence Checks that the specified window is displayed before continuing with the playback Window Image Captures and compares the client area of a window as a bitmap (the menu, title bar, and border are not captured). 8 About SQABasic Header Files SQABasic header files let you declare custom procedures, constants, and variables that you want to use with multiple scripts or SQABasic library source files. SQABasic files are stored in the SQABas32 folder of the project, unless you specify another location. You can specify another location by clicking Tools ® General Options. Click the Preferences tab. Under SQABasic path, use the Browse button to find the location. Robot will check this location first. If the file is not there, it will look in the SQABas32 directory. You can use Robot to create and edit SQABasic header files. They can be accessed by all modules within the project. SQABasic header files have the extension .sbh. 9 Adding Declarations to the Global Header File For your convenience, Robot provides a blank header file called Global.sbh. Global.sbh is a project-wide header file stored in SQABas32 in the project. You can add declarations to this global header file and/or create your own. To open Global.sbh: [...]... greater might be used in some circumstances, depending on the business application 5 Performance Testing Process Requirements Collection Preparation Requirement Collection Test Plan Preparation Test Plan Test Design Preparation Test Design Scripting Test Scripts Test Execution Pre Test & Post Test Procedure Test Analysis Preliminary Report Is Performance Goal Reached? NO Activity Deliverable Internal... Details Test data Transaction Traversal that is to be tested with sleep times Periodic status update to the client Deliverables Deliverable Sample Test Plan TestPlan.doc 3 Phase 3 – Test Design Based on the test strategy detailed test scenarios would be prepared During the test design period the following activities will be carried out: • Scenario design • Detailed test execution plan • Dedicated test. .. Software configurations Activity Performance- Stress Test, Load Test, Volume Test, Spike Test, Endurance Test • • • • • Work items Understand the system and application model Server side and Client side Hardware and software requirements Browser Emulation and Automation Tool Selection Decide on the type and mode of testing Operational Inputs – Time of Testing, Client and Server side parameters 1 2 Deliverables... performance test strategy The following artifacts will be produced during test execution period: • Test logs • Test Result Activity Test Execution • • • • Work items Starting the Pre Test Procedure scripts which includes start scripts for server monitoring Modification of automated scripts if necessary Test Result Analysis Report preparation for every cycle 1 Deliverables • Deliverable Test Execution... should reuse automated performance tests Automated performance tests can often be reused in many other automated test suites For example, incorporate the performance test suite into the stress test suite to validate stress scenarios and to identify potential performance issues under different stress conditions Tests are capturing secondary metrics when the instrumented tests have nothing to do with measuring... entire team with one place to go to determine the state of the system at any time In Test Manager you can plan, design, implement, execute tests and evaluate results With Test manager we can Create, manage, and run reports The reporting tools help you track assets such as scripts, builds, and test documents, and track test coverage and progress Create and manage builds, log folders, and logs Create and... database The objective of a performance test is to demonstrate that the system meets requirements for transaction throughput and response times simultaneously The main deliverables from such a test, prior to execution, are automated test scripts and an infrastructure to be used to execute automated tests for extended periods 1 What is Performance testing? Performance testing of an application is basically... Data pooling Activity Test Design Generation • • • • • Work items Hardware and Software requirements that includes the server components , the Load Generators used etc., Setting up the monitoring servers Setting up the data Preparing all the necessary folders for saving the results as the test is over Pre Test and Post Test Procedures 1 Deliverables Deliverable Sample Test Design TestDesign.doc 4 Phase... through the application and record the transactions with the tool Parameterization, Error Checks and Validations Run the script for single user for checking the validity of scripts Deliverables • Deliverable Test Scripts Sample Sample Script.doc 5 Phase 5 – Test Execution The test execution will follow the various types of test as identified in the test plan All the scenarios identified will be executed... repeated use Testers will not be able to record scripts in the first instance, or may not be able to execute a test for a reasonable length of time before the software, middleware or operating systems crash Realistic test environment The test environment should ideally be the production environment or a close simulation and be dedicated to the performance test team for the duration of the test Often . 1 Sample Test Automation Tool Rational offers the most complete lifecycle toolset (including testing) of these vendors for the. cases, test cases and a whole set of tools to support the process. 1 Rational Suite of tools Rational RequisitePro is a requirements management tool that