Explain about demand paging and page replacements

These are two very important concepts of memory management strategies in the computer operating systems namely demand paging and paging replacements. 

About Demand Paging

- Demand paging is just the opposite concept of the anticipatory paging. 

- Demand paging is actually a memory management strategy developed for managing the virtual memory.

- The operating system that makes use of demand paging technique, a copy of the disk page is made and kept in the physical memory whenever a request is made for it i.e., whenever a page fault occurs. 

- It is obvious that the execution of a process starts with none of its page loaded in to the main memory and follows by a number of page faults occurring one after the other until all of its required pages have been loaded in to the main memory. 

- Demand paging comes under the category of the lazy loading techniques. 

- This strategy follows that only if the process in execution demands a page, then only it should be brought in to the main memory. 

- That’s why the strategy has been named as demand paging. Sometimes it is even called as the lazy evaluation. 

- Page table implementation is required for using the demand paging technique.

- The purpose of this table is to map the physical memory to the logical memory. 

- This table uses a bit wise operator for marking a page as valid or invalid. 

The following steps are carried out whenever a process demands for a page:

1. An attempt is made for accessing the page.
2. If page is present in the memory the usual instructions are followed.
3. If page is not there i.e., is invalid then a page fault is generated.
4. Memory reference to a location in the virtual memory is checked if it is valid or not. If it’s an illegal memory access then the process is terminated. If not the requested page has to be paged in.
5. The disk operations are scheduled for reading the requested page in to the physical memory.
6. Restarting the instruction that raised the page fault trap.

- The nature of this strategy is itself of great advantage. 

- Upon availability of more space in the physical memory, it allows execution of many processes leading to a decrease in the context switching time.

- At the time of program start up, less latency occurs during loading. 

- This is because the inflow and outflow of the data between main memory and secondary memory is very less.

About Page Replacement

- When less number of real memory frames is available, it leads to invoking a page stealer. 

- This stealer searches through the PFT (page frame table) for pages to steal. 

- This table stores references to the pages which are required and modified. 

- If the requested page is found by the page stealer, it does not steal it but the reference flag is reset for that page. 

- So in the pass when the page stealer comes across this page, it steals this page. 

- Note that in this pass the page was flagged as un-referenced. 

- Any change made to the page is indicated by means of the modify flag.

- If the modify flag of the page to be stolen is set, then a page out call has to be made before the page stealer does its work. 

- Thus, the pages that form a part of the currently executing segments are written to so called paging space and the persisting segments are in turn written to the disk. 

- The page replacement is carried by the algorithms called the page replacement algorithms. 

- Besides this, these also keep a track of the faults. 

Explain the page replacement algorithms - FIFO, LRU, and Optimal

- Paging is used by most of the computer operating systems for the purpose of virtual memory management. 

- Whenever a page fault occurs, some pages are swapped in and swapped out. Who decides which pages are to be replaced and how? 

- This purpose is served by the page replacement algorithms. 

- Page replacement algorithms only decide which pages are to be page out or written to the disk when a page of the memory has to be allocated. 

- Paging takes place only upon the occurrence of a page fault.

- In such situations a free cannot suffice because either one is not available or because the number of available pages is less than threshold. 

- If a previously paged out page is reference again, then it has to be read in from the disk again. 

- But for doing this, the operating system has to wait for the completion of the input/ output operation. 

- The quality of a page replacement algorithm is denoted by the time it takes for a page in. 

- The lesser it is, the better the algorithm is. 

- The information about the access to page as provided by the hardware is studied by the page replacement algorithm and then it decides which pages should be replaced so that the number of page faults can be minimized. 

In this article we shall see about some of the page replacement algorithms.

FIFO (first – in, first – out): 

- This one being the simplest of all the page replacement algorithms has the lowest overhead and works by book – keeping in place of the OS. 

- All pages are stored in a queue in the memory by the operating system.

- The ones that have recently arrived are kept at the back while the old ones stand at the front end of the queue.

- While making replacement, the oldest page is selected and replaced. 

- Even though this replacement algorithm is cheap as well as intuitive, practically it does not perform well. 

- Therefore, it is rarely used in its original form. 

- VAX/ VMS operating systems make use of the FIFO replacement algorithm after making some modifications. 

- If a limited number of entries are skipped you get a partial second chance. 

Least recently used (LRU): 

- This replacement algorithm bears resemblance in name with the NRU. 

- However, difference is there which is that this algorithm follows that the page usage is tracked for a certain period of time. 

- It is based on the idea that the pages being used many times in current set of instructions will be used heavily in the next set of the instructions also. 

- Near optimal performance is provided by LRU algorithm in the theory however in practical it is quite expensive to be implemented. 

- For reducing the costs of the implementation of this algorithm, few implementation methods have been devised. 

- Out of these the linked list method proves to be the costliest. 

- This algorithm is so expensive because it involves moving the items about the memory which is indeed a very time consuming task. 

- There is another method that requires hardware support.

Optimal page replacement algorithm: 

- This is also known as the clairvoyant replacement algorithm. 

- The page that has to be swapped in, it is placed in place of the page which according to the operating system will be used in future after a very long time. - In practical, this algorithm is impossible to be implemented in case of the general purpose OS because approximate time when a page will be used is difficult to be predicted. 

Concept of page fault in memory management

Page fault is also known as the pf or #pf and can be thought of as a trap that the hardware raises for the software whenever the program tries to access a page that has been mapped to an address space in the virtual memory but has not been loaded in the main memory. 

In most cases, the page fault is handled by the operating system by helping in accessing the required page at an address space in the main or the physical memory or sometimes by terminating the program if it makes an illegal attempt to the access the page.

- Memory management unit is the hardware that is responsible for detecting the page faults and is located in the processor. 

- The software that helps the memory management unit in handling the page faults is the exception handling software and is seen as a part of the OS. 

- ‘Page fault’ is not always an error.

- These are often seen as a necessary role player in increasing the memory. 

- This can be made available to the software applications that makes use of the virtual memory of  the operating system for execution.

- Hard fault is the term used by the Microsoft instead of page fault in the resource monitor’s latest versions.

Classification of Page Faults

Page faults can be classified in to three categories namely:

1. Minor: 

- This type of fault is also called the soft page fault and is said to occur when the loading of the page in to the memory takes place at the time of the fault generation, but the memory management unit does not mark it as being loaded in the physical memory. 

- A page fault handler is included in the operating system whose duty is to make an entry for the page that is pointed to by the memory management unit. 

- After making the entry for it, its task is to give an indication that the page has been loaded. 

- However, it is not necessary that the page must be read in to the memory. 

- This is possible if the different programs share the memory and the page has been loaded in to the memory for the various applications. 

- In the operating systems that apply the technique of secondary page caching, the page can be removed from the working set of the process but not deleted or written to the disk.

2. Major: 

- Major fault is actually a fault that many operating systems use for increasing the memory for the program that must be available as demanded by the program. 

- The loading of the parts of the program is delayed by the operating system from the disk until an attempt is made by the program for using it and generating the page fault.

- In this case either a non – free page or a page in the memory has to be found by the page fault handler. 

- When the page is available, the data from it can be read by the operating system to the new page in the main memory, thus easily making an entry for the required page.

3. Invalid: 

- This type of fault occurs whenever a reference is made to an address that does not exists in the virtual address space and therefore it has no page corresponding to it in the memory. 

- Then the code by which the reference was made has to be terminated by the page fault handler and give an indication regarding the invalid reference. 

What is the cause of thrashing? How does the system detect thrashing? Once it detects thrashing, what can the system do to eliminate this problem?

- Thrashing takes place when the sub-system of the virtual memory of the computer system is involved in a state of paging constantly.

- It rapidly exchanges data in the memory with the data available on the disk excluding level of processing of most of the applications. 

- Thrashing leads to the degradation of the performance of the computer or may even cause it to collapse. 

- The problem may further worsen until the issue is identified and addressed. 

- If there are not enough pages available for the job, it becomes very likely that your system will suffer from thrashing since it’s an activity involving high paging. 

- This also leads to high rate of page fault. 

- This in turn cuts down the utilization of the CPU. 

- Modern systems utilize the concept of the paging system for executing many programs.

- However, this is what makes them prone to thrashing. 

- But this occurs only if the system does not have at present sufficient memory as required by the application or if the disk access time is too long. 

- Thrashing is also quite common in the communication systems where the conflicts concerning the internal bus access is common. 

- The order of magnitude or degree by which the latency and throughput of a system might degrade depends up on the algorithms and the configuration that is being used. 

- In systems making use of virtual memory systems, workloads and programs presenting insufficient locality of reference may lead to thrashing. 

- Thrashing occurs when the physical memory of the system is not able to contain in itself the workload or the program. 

- Thrashing can also be called as the constant data swapping.

- Older systems were low end computers i.e., the RAM they had was insufficient to be employed in modern usage patterns. 

- Thus, when their memory was increased they became noticeably faster. 

- This happened because of the availability of more memory which reduce the amount of swapping and thus increased the processing speed. 

- IBM system/ 370 (mainframe computer) faced this kind of situation. 

- In it a certain instruction consisted of an execute instruction pointing over to another move instruction. 

- Both of these instructions crossed the page boundary and also the source from which the data has to be moved and the destination where it was to be placed both crossed the page boundary. 

- Thus, this particular instruction altogether required 8 pages and that too at the same time in memory. 

- Now if the operating system allocated less than 8 pages, a page fault is sure to occur. 

- This page fault will lead to thrashing of all the attempts of restarting the failing instruction. 

- This may even reduce the CPU utilization to almost zero!

How can a system handle thrashing?

For resolving the problem of thrashing, the following things can be done:

1. Increasing the amount of main memory i.e., the RAM in the system. This is the best ever solution for this and will be helpful for a long term also.

2. Decreasing the number of programs to be executed by the system.

3. Replacing the programs that utilize heavy memory with their less memory utilizing equivalents.

4. Making improvements in the spatial locality.

- Thrashing can also occur in cache memory i.e., the faster storage space that is used for speeding up the data access. 

- Then it is called cache thrashing. 

- It occurs when the cache is accessed in a way that it leaves it of no benefit. 

- When this happens many main memory locations compete with each other for getting the same cache lines that it turn leads to a large number of cache misses.

Explain SlimDog - Web Functional/Regression Test Tool

About SlimDog

- SlimDog is a web application testing tool that is based on simple script i.e., the httpunit. 

- The tool comes with a range of commands that help you to work with forms, navigating between the web pages and checking the table contents. 

- The hard task of writing lengthy xml files and JUnit test cases, the slimdog allows the users to create simple text scripts. 

- Each command is a test node that is contained in every line of the script.

- As such all commands contained in a file are treated as a test case and processed as the same. 

- Every command has a syntax that is quite simple as well as easy to learn. 

- If you want, you can form a test suite by combining several test scripts. 

- The results of the tests executed are written as an html page or file to the console. 

How to use SlimDog?

- To use slimdog, firstly you need to download its latest version from its web site. 

- The application will be in zipped form. 

- You need to extract the files to a directory of your choice. 

- Next step is to create a test directory. 

- After this you can start creating tests and save them in the test directory you just created. 

- After you have created the test, your next step is to get the html content. 

- You can run the tests from the command line. 

- After obtaining the results save them to a file. 

- Be careful that the file in which you are saving the result should be defined using the –o argument. 

- You can even navigate from one page to another. 

- All files in the test directory can be run as a test suite. 

- Every test case file must end with .test extension so that it becomes recognizable.

- You can even use a proxy. 

- The slimdog commands can even be used with the JUnit test cases.

- However, running a test case is the easiest way. 

- Firstly, the web tester needs to be instantiated and all commands need to be added through the parse line method.

- You do not have to worry about the syntax since it is the same as that of the script files. 

- After this runtest() method can be called and web test results can be obtained. 

General SlimDog Commands

Below we shall mention some general slimdog commands:

1. Get_html: This command is for establishing a connection with the given URL and thus reading its content. The read content then can be used later. The parameter to this command is the URL itself and it supports variables.
2. Check_title: Parameter for this command is the required title and it is of the type test. The title of the page that you specify is checked against the given title. There is one thing about this test which is that if it fails, the entire test will fail.
3. Set_proxy: The parameters for this command are the proxy port and host. It is of the type command.
4. Check_link (missing): The parameter for this command is the text within the tag and this one is also of the type test.
5. Check_text: The text to be found is passed as a parameter to this command and it is of the type test.
6. Click_link: The argument for this is the text within the tag. It is of the type command.
7. Seturlprefix: The parameter here is the URL prefix. This URL prefix is used as the base URL for other tests. It is of the type command.
8. Enable java_script: Parameter is either true or false. This command disables and enables the JavaScript based on the argument passed.

Explain Janova - Web Functional/Regression Test Tool

About Janova Testing Tool

- Janova is another tool in the class of the web testing tools but certainly better since it is automated. 

- The major characteristic feature that sets this testing tool apart from the others is its capability of running the tests in the cloud with security and reliability. 

- Janova can be configured using the project structures of features such as pages, test scripts and flows for accessing the web – based applications and defining its requirements in natural language such as English. 

How the application is supposed to work is described by its features.

- Firstly, the feature is created, verification elements are defined by the user that is supposed to be on that particular web page. 

- The tool also provides the detailed result reports concerning the tests performed. 

- Janova is all about automated testing in cloud which is powerful, effective and simple. 

- Using Janova, you can write tests in simple English. 

- Therefore, the need for coding is eliminated. 

- The tests are executed via the power of the cloud. 

- The detailed reports help you to understand the results of your test. 

- The plain English business rules are turned in to the tests by Janova. 

- Since the tests are run in the cloud, the need for keeping the software up to date and disparate files is reduced.

- Also, you don’t need to spend thousands of dollars on the maintenance of the software testing equipment.

- For producing the code – free business requirements the features, flows and pages. 

- These requirements then become the automated tests that can be executed in the cloud at a speed that is 20 times faster than the usual web testing tools. 

How Janova actually works?

- Janova offers such an automated testing solution that lets you test an application across various environments. 

- You can use the power of the cloud for multiplying the effective workload and at the same time can track the progress of your development team. 

- Janova has been designed in such a way that the brittleness that other testing solutions have can be avoided.

- If the business requirements undergo any changes, they are automatically reflected in the tests since the tests are requirements and requirements are tests. 

- Therefore, changes made in one are reflected in the other.

- Using just plain English you can create a test in very less time that would be capable of creating and updating the variables automatically.

- It would also link the variable through the system of features, steps, scenarios, and pages.

-The tests are defined at a very high level allowing you to implicitly understand the desired outcome of the test. 

- Once you are done with the creation of the features and scenarios, you can define the variables by right – clicking on the ‘inspect element’ option with any tools preferred by the developer and moving that info in to the page files. 

What if you encounter an error in the page files? 

- Janova provides solution for this also. 

- You can edit it here and the changes will be retroactively be updated within the tests. 

- The application under test goes through the following stages:

1. Janova application
2. Broker
3. Workers
4. Secure access
5. Results

- Janova operates through the cloud – based system of workers.

- It scales and delegates the processing power automatically ensuring that you get results for your tests as fast as possible.

- The plain language syntax is converted in to a testing script. 

- This script is then distributed throughout the cloud.

- Janova has partnered with GoodData (which is a business intelligence provider) in order to provide it users with a more powerful analytic suite.

Explain Cucumber Testing Tool?

A need was felt for a tool that could create and run automated acceptance tests that were developed in so called BDD or behavior driven development style. Thus, cucumber testing tool came in to existence. 

About Cucumber Testing Tool

- The software for this tool has been developed in ruby programming language. 

- However, the cucumber testing tool does work for the projects beyond the ruby level. 

- For some ruby, cucumber testing tool is like a bridge to go to the target language. 

- For other, gherkin parser still continues to be relevant while they use the target language for the implementation purpose.

- There are certain feature documentations that are created in business – facing text and these can also be executed with the help of cucumber testing tool. 

- Features might be defined using one or more than one scenarios. 

- These are executed using the ruby definition of the test implicit comprising of few steps. 

- For the ruby tool box, the cucumber testing tool proved to be the most popular testing frame work in the month of January 2012. 

- The leading frame work was RSpec. 

- In the same year in the month of April, the cucumber testing tool was moved to a category of the acceptance test frameworks. 

- A survey was carried out which revealed that cucumber testing tool stands 5^th in the ranking of the popular testing frameworks being used by the startup companies.

- Cucumber is just an implementation of the behavior driven development based up on ruby.

- Using it, the user can describe how the system behaves with some natural language comprising of some specific keywords. 

- Firstly, a feature file is created explaining a feature of the software system or application as well as certain scenarios pertaining to a number of different test situations. 

- Secondly, step definitions are written in ruby programming language that explains the purpose of that particular step. 

- Writing those definitions in ruby language provides flexibility in the execution of the test cases. 

- The testing tool comes with definitions for an acceptance testing tool called webrat. 

- This tool can be used for simulation of the browser not having javascript support. 

- It also provides option for making a combination with water that is a web automation frame work and is used for implementing the web automation tests based up on web browser.

- Using cucumber, with this combination counts as a traditional way of using it but anyways it works quite well. 

- In testing using cucumber, a feature is tested against a number of test scenarios that might describe several operations. 

- The step definitions part needs to be explained so that the tool knows what it has to do next. 

- In some of the cases, water is used with water – web driver gem and Rspec gem. 

- Constants can be defined as a reference to the browser and for web.

- Hash PAGES is not required in every case but proves to be beneficial when there are a number of pages involved. 

- The tests thus developed can be executed either when the full web site is ready or during the implementation phase itself. 

- Even if you decide to go with the second option, you will have to run the test one more time when the next release goes out. 

- You have a third option i.e., for using the test as a stand – alone set for the web site. 

- Another plus point of the cucumber testing tool is that it displays in quite a formatted way that displays steps that were both successful and failure. 

- Green color is used for displaying successful steps and red is used for the failed ones. 

- All that has been described for the cucumber implies for the water web testing frame work also. 

How to add and match defects in Test Director?

Location of the defects and their effective repair forms an inseparable part of the application development and indeed of the test director testing process. Defects can be submitted by almost everyone involved with the development process such as the developers, end users and of course testers. The test director eases all the testing processes and thus defects can be submitted through it and can be tracked until they are appropriately repaired. 

In this article we shall discuss the following two things:

1. Adding defects in the test director and
2. Matching defects in test director

Steps in adding defects in Test Director

Whenever a defect is submitted to the test director it is processed through the following  four stages:

1. New
2. Open
3. Fixed
4. Closed

Addition of the defects to the test director can be carried out at almost any stage of the test process. Below we state the steps that you need to follow in order to add the defects in test director:

1. Open the test director project with which you are concerned and log on to it.
2. Next step involves displaying the defects module by clicking on the defects tab. The defect data will be displayed by the defects grid in a grid where each row is a representation of an individual defect record.
3. Clicking on the add defect button will open up the ‘add defect’ dialog box. The fields displayed in red color are mandatory to be filled up.
4. Fourth step involves describing the defect by providing the following details:

a) Summary: i.e., what problem the defect actually caused.

b) Category

c)  Severity

d) Subject

e) Detected in version

f) Description:

It includes the part of the code where the defect was discovered and 

what problem was actually encountered.

5. Now you need to attach the URL address for the page where the defect was found by clicking on the Attach URL button. Clicking on that button will open up a attach URL dialog box. There type the address of the page and click OK. This URL will be displayed above the description box by the test director.
6. Next run a spell check for the text in the description box. If any errors are found follow the replacement suggestions.
7. Click on the submit button to submit the defect to the test director project.
8. Finally, close the add defect dialog box by clicking on the close button. The defect will be added to the defect grid.

How to match defects in Test Director

- The purpose of matching the defects is to find similar defects so that the duplicate ones can be eliminated from the project. 

-  Every time a new defect is added the list of keywords is stored by the test director from the description and summary fields. 

-  The stored keywords are then used for matching the defects. 

- Articles, coordinate conjunctions, wildcards and Boolean operators are ignored by the test director while matching the two tests. 

- Below mentioned steps are for matching defects in test director:

1. Like for adding the defects this also requires displaying the defects module. Do this by clicking on the defects tab.
2. From the defects grid select the one you want to match. If in case you cannot find the required test search it using the clear filter/ sort button.
3. Now click on the find similar defects button to find similar defects. The results will be displayed in the similar defects dialog box by the test director.The defects are searched based up on percentage of the similarity detected.
4. Finally, click on the close button to close the similar defects dialog box. 

What is the Document Object Model (DOM) browser extension?

In this article we shall talk about the DOM browser extension of the silk test. But before coming to this topic we shall discuss a little about the DOM or the document object model. 

What is Document Object Model (DOM)?

- There was a need for a language and cross platform independent convention for the representation and interaction with the objects consisted in XHTML, HTML, XML etc documents. 

- Out of this need, only document object model was born. 

- Certain object methods are used for addressing as well as manipulating the objects present in the DOM tree.

- It is in the API or application programming interface where the public interface of the document object model is specified. 

- For rendering any of the documents mentioned above, an internal model quite similar to the document object model is used by most of the web browsers. 

- The nodes of all the documents are organized in a tree like structure which is commonly known as the DOM tree. 

- The top most node of this tree is termed as the document object.

- The HTML is downloaded in to the local memory and is parsed whenever a document is rendered in a browser. 

- Parsing is done using the DOM for the construction of the internal data structures that are employed for displaying the page in the browser window. 

- DOM’s application programming interface is also used by the java script for the inspection and modification of a web page. 

Use of DOM Browser Extension in SilkTest

- It acts as an add – on component that helps a big deal in the testing of the web applications. 

- A direct communication with the web browser is established by the DOM browser extension so that the recognition, categorization and manipulation of the objects on a web page can be made possible. 

- This direct communication with the web browser is established by the DOM browser extension.

- It is done by actually working with the HTML code rather than making use of the visual pattern recognition as relied on by the other such extensions or add ins. 

- The technique of visual pattern recognition is usually used by the virtual object browser extension. 

- The DOM browser extension identifies an object in a web application through the following steps:

1. The web browser window in which the application is current executing is identified.
2. Then the web UI object is identified that is based up on the HTML element representing the UI object.

- The whole identification of a UI web application object is possible only with the concatenation of the HTML element identification and the browser window identification.

- This document object model of the silk test makes use of the DOM standard stated by the W#C or World Wide Web consortium. 

- However, this DOM standard is currently supported by two web browsers namely Netscape 6 and internet explorer 5+ versions. 

- These two web browsers allow the external applications such as the silk test for making direct queries to the browser for obtaining information regarding the web page that is currently being displayed. 

- When the DOM browser extension is enabled on the host machine, an extension file is included so that the extension classes are made available to the user. 

- The silk test always makes sure that the extension classes are always visible in the library browser. 

- This is done so by addition of the of the help file of the extension (browser.ht) to the help files. 

- The properties defined for the DOM browser extension are merged with the default property sets which include the following:

1. Color
2. Font
3. Values and
4. Location

What is the use of rapid test script wizard?

Sometimes it may happen that you may require test cases within shortest period of time possible may be because you have a dead line to cover up for delivering some results or you have got to do some adhoc testing of the software system or application or you may have to complete creating your GUI map file as quickly as possible. 

Whatever the reason you may be having, the rapid test script wizard helps you well in all such situation. The rapid test script wizard is another quite a helpful tool from the winrunner for a quick creation of many automated tests as well as GUI maps. And because of this ability of this tool, it has been named as the “rapid test script wizard”. 

What is a rapid test script wizard and what is its use?

- More than a software, the rapid test script wizard is more like a tool. 

- It is a tool that helps in making your complex and lengthy tasks simpler and shorter. 

- The first step of the rapid test script wizard is to gather information and details from you about the creation of the GUI map files and automated tests in a series of steps.

- After having gathered all the necessary and sufficient relevant data, the wizard proceeds further in its work. 

- Information is gathered from the user in form of some questions displayed on a series of pages. 

- Once the user has answered all of these questions the rapid test script wizard creates the required product based up on the answers that the user provided it. 

- The tasks that can be performed by rapid test script wizard are:

1. Automatic learning of the all the GUI objects that are present in the application.
2. Saving these GUI objects in to a GUI map file.
3. Creating 3 types of tests.

- A full suite of basic test cases is created by the rapid test script wizard based up on whatever it has learned regarding the graphical user interface of the software system and application. 

- The rapid test script wizard has ultimately cut down the requirement of the testers for the creation of test suites one at a time. 

- This, the rapid test script wizard does by walking through the application software itself and by subjecting the test scripts to reverse engineering taking them directly from the application software. 

- Not only the GUI, but also the rapid test script wizard learns about all the windows and objects that form a part of the software system or application. 

- The paid test script wizard holds good for the client server application. 

- There are some cases in which the winrunner fails to learn about the graphical user interface of the application software. 

- In such cases, with the help of rapid test the winrunner can be made to learn the GUI objects present in the application software. 

- In rapid test script wizard, the application window is shown to the winrunner and the test scripts are recorded and stored in a temporary folder. 

- This is to be done before subjecting the software system or application to any other type of testing. 

- This is so because if this is not done then there are chances that while running the tests, the software system or application may crash or hang. 

- The windows in the application software are opened up one by one in a systematic way by the rapid test script wizard. 

- One thing that should be noted is that this tool i.e., the rapid test script wizard is not available in the winrunner advance mode i.e., in the GUI map file per test mode.