Topic: Best Practices during Recording in IBM RFT

Message

This article describes useful tips we can take advantage of, while recording in RFT

1) Best Practices of changing the State of Application while Recording:

a) Changing the State of Application while Recording Verification Point:
# When we pause the recorder for creating a verification point, we should bear it in mind that if we happen to make any change in the state of the application, it is going to affect our script. 

# If we change the state of the application while the recorder is paused; all actions recorded after this event could prevent the script from playing back, since the application is in the incorrect state to play back the actions. 
# Before beginning to create a verification point, we need to put the application in a state, which is ultimately desired. For example, if we need to do some actions in the user interface to locate the object desired to be tested, we need to put the application in that state before we start the verification point.

# In the "Select an Object page" of the Verification Point and Action Wizard, we can use the delayed object selector to pause the recorder while we access an object in the application. All actions performed while the delay is in effect will not be recorded.

Complete article is available at:

Author	Message
yogindernath Groupie Joined: 27Oct2008 Location: India Online Status: Offline Posts: 52	Topic: Best Practices during Recording in IBM RFT Posted: 25Jan2009 at 5:29am
	This article describes useful tips we can take advantage of, while recording in RFT 1) Best Practices of changing the State of Application while Recording: a) Changing the State of Application while Recording Verification Point: # When we pause the recorder for creating a verification point, we should bear it in mind that if we happen to make any change in the state of the application, it is going to affect our script. # If we change the state of the application while the recorder is paused; all actions recorded after this event could prevent the script from playing back, since the application is in the incorrect state to play back the actions. # Before beginning to create a verification point, we need to put the application in a state, which is ultimately desired. For example, if we need to do some actions in the user interface to locate the object desired to be tested, we need to put the application in that state before we start the verification point. # In the "Select an Object page" of the Verification Point and Action Wizard, we can use the delayed object selector to pause the recorder while we access an object in the application. All actions performed while the delay is in effect will not be recorded. Complete article is available at:
	http://www.softwaretestinggenius.com A Storehouse of Complete Knowledge on Software Testing & QA under one Roof Post Resume: Click here to Upload your Resume & Apply for Jobs

	IP Logged


One Stop Testing Forum : Testing Tools @ OneStopTesting : Rational Robot @ OneStopTesting