IBM? Rational? Functional Tester for Java? IBM? Rational? Functional Tester for Java? Playing back an automated test script This module provides an overview of playing back an automated test script using IBM Rational Functional Tester for Java. Course objectives Course objectives General concepts Test development Regression testing Running a recorded test Setting playback preferences Running the script Examining the results Playback log Investigating warning and error messages Summary 2 This course covers topics related to playing back an automated test script. It discusses test development and regression testing, and goes through the steps of setting playback preferences and executing the script. This module also reviews logs, including warnings and errors in the logs. General concepts General concepts Test development Verify the script Establish a baseline Regression testing Compare the latest build Identify defects 3 There are two phases of the automated test script development process that a script is played back in: test development and regression testing. Test development includes recording, refining, and testing a script. After recording, a user can edit a script to add comments, perform additional actions, or use an external data source. During test development, play back a script to verify that it plays back successfully and works as intended, and to establish a baseline against which to compare future builds of the application under test. Regression testing reveals differences introduced into the application under test since the last build. Evaluate these differences to determine whether they are defects or deliberate changes. During regression testing, play back a script to compare the latest build to an established baseline, and to identify defects caused to existing functionality by new code development. Running a recorded test Running a recorded test Setting playback preferences 4 Before playing back a recorded script, ensure that the application under test is in the same state it was in when the script was recorded. Any applications and windows that were open, displayed, or active when the script was recorded must be open, displayed, or active before playback is started. Running a recorded test Running a recorded test Setting playback preferences 5 The tester has the option to set playback preferences. From the Window menu in Functional Tester, select ?Preferences.? In the Preferences window that opens, in the left pane, expand ?Functional Test,? then expand ?Playback.? Five different sets of playback preferences can be set here. Logging allows testers to choose what kind of log, HTML, or Text they want to generate at the end of playback. Other available logging choices include ?Prompt before overwriting an existing log,? ?Display log viewer after script playback,? and ?Don?t show script launch wizard.? Monitor allows the tester to view the script name, the number of the line being executed, the status icons, and a description of the action in progress as the script is being played back. Mouse Delay sets the delay in seconds to occur before every mouse up or down action. Other Delays sets the delay in seconds to occur before every key up or down action, or before performing a test object action. Script Assure helps a script to play back successfully, even after the update of the application under test. Each object in a test object map has a set of recognition properties, typically established during recording. If objects in the application under test have changed, scripts can still be played back in Functional Tester using the Script Assure feature to control object-matching sensitivity. If the tester chooses to ignore these selections, the default settings are applied before playing back the script. Running a recorded test Running a recorded test Running the script 6 Run Functional Test Script Once the playback preferences are set, the script is ready to execute. Open the script for playback, and click the ?Run Functional Test Script? icon. A tester can also right-click the script in the Functional Test Project view, then click Run in the menu. Running a recorded test Running a recorded test Running the script 7 A Select Log window opens. By default, a log file named after the script appears. Testers have the option to rename this. Click Next. A Specify Playback Options window opens. Here, testers can specify any arguments needed to run the script, and can set the datapool iteration count. When complete, click Finish. Functional Tester now plays back the tests. Note that if this test was run previously, a prompt appears asking for confirmation to overwrite the log Examining the results Examining the results Playback log 8 After playback is complete, the results display in an HTML log in a browser window. HTML is the default logging option. If the tester chose a different format for logging, the log displays in that format. This log is also found in the log folder in the Functional Test Projects view. The left frame of the log provides quick navigation to important information. The right frame provides details regarding which parts of the script passed or failed. Examining the results Examining the results Investigating warning and error messages 9 Typical errors or warning messages in Functional Tester include ?Object Not Found? and ?Object Recognition is weak.? Review the error details in the application log to determine if an object is missing from the previous version on which the script was recorded. This should indicate why playback produces one of these error messages. Take the necessary steps to correct these errors or warnings. This ranges from removing the missing objects from the object map and script to updating the recognition properties of the object in question. Examining the results Examining the results Investigating warning and error messages 10 Another part of the log is failed verification points. Find the failed verification point in the log and click the ?View Results? link in that section. The verification point comparison window appears. This window shows the expected value recorded during the script recording and the actual value the script found during the playback. The difference in the value is highlighted in red. Summary Summary This module provided an overview of playing back an automated test script using IBM Rational Functional Tester for Java. The Tester can: Set playback preferences Execute the script Examine the results in the log 11 This module provided an overview of playing back an automated test script using IBM Rational Functional Tester for Java. In this process, the tester sets playback preferences accordingly, executes the script, and examines the results in the log, searching for any problems. Feedback Feedback Your feedback is valuable You can help improve the quality of IBM Education Assistant content to better meet your needs by providing feedback. Did you find this module useful? Did it help you solve a problem or answer a question? Do you have suggestions for improvements? Click to send e-mail feedback: mailto:iea@us.ibm.com?subject=Feedback_about_RFTPlayback.ppt This module is also available in PDF format at: ../RFTPlayback.pdf You can help improve the quality of IBM Education Assistant content by providing feedback. Trademarks
IBM® Rational® Functional Tester for Java™ IBM® Rational® Functional Tester for Java™ Playing back an automated test script This module provides an overview of playing back an automated test script using IBM Rational Functional Tester for Java. Course objectives Course objectives General concepts Test development Regression testing Running a recorded test Setting playback preferences Running the script Examining the results Playback log Investigating warning and error messages Summary 2 This course covers topics related to playing back an automated test script. It discusses test development and regression testing, and goes through the steps of setting playback preferences and executing the script. This module also reviews logs, including warnings and errors in the logs. General concepts General concepts Test development Verify the script Establish a baseline Regression testing Compare the latest build Identify defects 3 There are two phases of the automated test script development process that a script is played back in: test development and regression testing. Test development includes recording, refining, and testing a script. After recording, a user can edit a script to add comments, perform additional actions, or use an external data source. During test development, play back a script to verify that it plays back successfully and works as intended, and to establish a baseline against which to compare future builds of the application under test. Regression testing reveals differences introduced into the application under test since the last build. Evaluate these differences to determine whether they are defects or deliberate changes. During regression testing, play back a script to compare the latest build to an established baseline, and to identify defects caused to existing functionality by new code development. Running a recorded test Running a recorded test Setting playback preferences 4 Before playing back a recorded script, ensure that the application under test is in the same state it was in when the script was recorded. Any applications and windows that were open, displayed, or active when the script was recorded must be open, displayed, or active before playback is started. Running a recorded test Running a recorded test Setting playback preferences 5 The tester has the option to set playback preferences. From the Window menu in Functional Tester, select “Preferences.” In the Preferences window that opens, in the left pane, expand “Functional Test,” then expand “Playback.” Five different sets of playback preferences can be set here. Logging allows testers to choose what kind of log, HTML, or Text they want to generate at the end of playback. Other available logging choices include “Prompt before overwriting an existing log,” “Display log viewer after script playback,” and “Don’t show script launch wizard.” Monitor allows the tester to view the script name, the number of the line being executed, the status icons, and a description of the action in progress as the script is being played back. Mouse Delay sets the delay in seconds to occur before every mouse up or down action. Other Delays sets the delay in seconds to occur before every key up or down action, or before performing a test object action. Script Assure helps a script to play back successfully, even after the update of the application under test. Each object in a test object map has a set of recognition properties, typically established during recording. If objects in the application under test have changed, scripts can still be played back in Functional Tester using the Script Assure feature to control object-matching sensitivity. If the tester chooses to ignore these selections, the default settings are applied before playing back the script. Running a recorded test Running a recorded test Running the script 6 Run Functional Test Script Once the playback preferences are set, the script is ready to execute. Open the script for playback, and click the “Run Functional Test Script” icon. A tester can also right-click the script in the Functional Test Project view, then click Run in the menu. Running a recorded test Running a recorded test Running the script 7 A Select Log window opens. By default, a log file named after the script appears. Testers have the option to rename this. Click Next. A Specify Playback Options window opens. Here, testers can specify any arguments needed to run the script, and can set the datapool iteration count. When complete, click Finish. Functional Tester now plays back the tests. Note that if this test was run previously, a prompt appears asking for confirmation to overwrite the log Examining the results Examining the results Playback log 8 After playback is complete, the results display in an HTML log in a browser window. HTML is the default logging option. If the tester chose a different format for logging, the log displays in that format. This log is also found in the log folder in the Functional Test Projects view. The left frame of the log provides quick navigation to important information. The right frame provides details regarding which parts of the script passed or failed. Examining the results Examining the results Investigating warning and error messages 9 Typical errors or warning messages in Functional Tester include “Object Not Found” and “Object Recognition is weak.” Review the error details in the application log to determine if an object is missing from the previous version on which the script was recorded. This should indicate why playback produces one of these error messages. Take the necessary steps to correct these errors or warnings. This ranges from removing the missing objects from the object map and script to updating the recognition properties of the object in question. Examining the results Examining the results Investigating warning and error messages 10 Another part of the log is failed verification points. Find the failed verification point in the log and click the “View Results” link in that section. The verification point comparison window appears. This window shows the expected value recorded during the script recording and the actual value the script found during the playback. The difference in the value is highlighted in red. Summary Summary This module provided an overview of playing back an automated test script using IBM Rational Functional Tester for Java. The Tester can: Set playback preferences Execute the script Examine the results in the log 11 This module provided an overview of playing back an automated test script using IBM Rational Functional Tester for Java. In this process, the tester sets playback preferences accordingly, executes the script, and examines the results in the log, searching for any problems. Feedback Feedback Your feedback is valuable You can help improve the quality of IBM Education Assistant content to better meet your needs by providing feedback. Did you find this module useful? Did it help you solve a problem or answer a question? Do you have suggestions for improvements? Click to send e-mail feedback: mailto:iea@us.ibm.com?subject=Feedback_about_RFTPlayback.ppt This module is also available in PDF format at: ../RFTPlayback.pdf You can help improve the quality of IBM Education Assistant content by providing feedback. Trademarks