PK77434: RFT: Browser ready state returning 4 before load complete

IBM Rational Functional Tester Version 8.0.0.1

APAR status

• Closed as program error.

Error description

• The client has scripts that worked fine in RFT 6.1 but fail duri
  ng playback in RFT 7.0.1.2. They are testing against a PeopleSof
  t web-based app in IE6 on XP SP2 boxes.
  
  
  
  The utilize the following command to get the browser state:
  browser_htmlBrowser().getProperty('.readyState'))
  
  After reach series of actions, they wait for the browser state t
  o equal 4 before continuing.
  
  
  After several functions are performed, the AUT begins to lag and
   their wait state code does not work as they intend. They then s
  ee object not found exceptions.
  
  
  
  This problem only exists in RFT 7.x. The same scripts against th
  e same AUT in the same browser (IE6) work fine in RFT 6.x.
  
  
  
  The client wants to know how they can modify their code to make
  it work properly with RFT 7. They requested that I show the info
  rmation they submitted to someone from development to seek advic
  e.
  
  
  They are currently in the testing phase of RFT 7, but they have
  a scheduled roll out of RFT 7 early next week. They require a so
  lution by
  Friday. They stated that this is a Sev1 issue.
  I committed to the client that we would have an update for them
  on Wednesday 10/15/2008 by the end of the business day.
  The client provided the following code snippets:
  public void browserWait(TestObject myBrowser) {
  while
  (!myBrowser.getProperty('.readyState').toString().equalsIgnoreCa
  se('4'))
  {
  sleep(0.5);
  }
  }
  and
  public void browserWait123() {
  System.out.println('FIRST Browser State: ' +
  browser_htmlBrowser().getProperty('.readyState'));
  while
  (!browser_htmlBrowser().getProperty('.readyState').toString().eq
  ualsIgno
  reCase('4')) {
  System.out.println('Browser State: ' +
  browser_htmlBrowser().getProperty('.readyState'));
  sleep(2);
  }
  }
  

Local fix

Problem summary

• Caching the ready state is causing the issue for the
  automated scripts, which are developed using dynamcic find()
  

Problem conclusion

• Handled the issue to return readyState properly
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  RAT FUNC TESTER

• Fixed component ID

  5724G2503

Applicable component levels

• R700 PSN

     UP