QA Forums
Welcome on the QA Forums.

To take full advantage of everything offered by our software testing & Quality forums, please log in if you are already a member or join our community if you're not yet.... Smile
Search
 
 

Display results as :
 


Rechercher Advanced Search

Navigation
 Portal
 Index
 Memberlist
 Profile
 FAQ
 Search
Who is online?
In total there is 1 user online :: 0 Registered, 0 Hidden and 1 Guest

None

[ View the whole list ]


Most users ever online was 35 on Tue Sep 23, 2014 10:22 pm
November 2017
MonTueWedThuFriSatSun
  12345
6789101112
13141516171819
20212223242526
27282930   

Calendar Calendar


The Script Recording Process in OpenSTA

View previous topic View next topic Go down

The Script Recording Process in OpenSTA

Post  puneet on Thu Oct 07, 2010 11:33 pm

Script Modeler creates a Script exactly as the browser requested the Web pages and their contents. They are created by the Gateway and consist of SCL code, including GET, POST and HEAD commands, which represent corresponding HTTP/S instructions.

Scripts represent HTTP/S browser requests in SCL code and are saved in a .HTP file. During the same recording session the corresponding WAE responses are recorded by the Gateway in a .ALL file. This includes DOM, HTML and Web page structure data. The full detail of a Web session is stored in these two files.

After you have clicked the Record button in the Capture/Replay Toolbar and entered the first URL in your browser's Address text box, the WAE responds by sending the HTTP/S data that forms the content of the Web page displayed by your browser.

Loading a Web page involves parsing or compiling the Web page structure from the raw HTTP/S data returned by the WAE in response to the URL or PRIMARY GET. The content is then rendered on screen by the browser whilst concurrently making additional, asynchronous requests on other TCP connections via secondary GETs for the remaining contents of the Web page. The browser continues to issue requests and render any remaining content until the Web page is fully loaded. The Gateway records and formats this information.

Browser requests hit the target WAE via the Gateway, across the Internet or other network. Browser requests are recorded by the Gateway as a Script (.HTP file). WAE responses are recorded by the Gateway in a .ALL file.

Note: OpenSTA Console refers to a computer which has an installation of OpenSTA. This includes the OpenSTA Architecture and Commander and it may also include the Repository, where all Test related files and results are stored. The PC will also have a Web browser installed and is typically the home for the Gateway. In this diagram the Gateway is shown as separated from the OpenSTA Console to clarify the Script recording process.

puneet

Posts : 21
Reward Points : 41
Join date : 2010-08-22

View user profile

Back to top Go down

View previous topic View next topic Back to top

- Similar topics

 
Permissions in this forum:
You cannot reply to topics in this forum