What is Polling?

- Polling is often referred to as the polled operation.

- When the statuses of the external devices are actively sampled by a client program just like a synchronous activity is referred to as the polling. 

- The common use of the polling is in the input and output operations. 

- In rare cases, polling is also called as the software driven I/O or just simply as polled I/O. 

- As and when required, polling is also carried out with the busy waiting synonymous. 

- Polling is then referred to as the busy–wait polling. 

- In this case whenever it is required to carry out an input/ output operation, the system just checks the status of the device required for fulfilling this operation until it is idle. 

- When it becomes idle it is accessed by the I/O operation. 

- Such polling may also refer to a state in which the status of the device is checked again and again for accessing it if idle. 

- If the device is occupied, the system is forced to return to some other pending task. 

- In this case the CPU time is wasted less when compared to what happens in busy waiting. 

- However, this is not a better alternative to interrupt driven I/O polling. 

- In single purpose systems that are too simple, using busy-wait polling is perfectly fine if the system cannot take any action until the I/O device has been accessed. 

- But traditionally, the polling was thought to be a consequence of the operating systems and simple hardware that do not support multitasking. 

- The polling works intimately with the low level hardware usually. 

- For example, a parallel printer port can be polled for checking whether or not it is ready for printing another character. 

- This involves just the examination of a bit. 

- The bit to be examined represents the high or low voltage stage of the single wire in the cable of the printer during the time of reading. 

- The I/O instruction by which this byte is read is also responsible for transferring the voltage state directly to the eight flip flops or circuits. 

- These 8 flip flops together constitute one byte of a register of CPU. 

Polling also has a number of disadvantages. 

- One is that there is limited time for servicing the I/O devices. 

- Polling has to be done within this time period only. 

- But in some cases there are many devices to be checked which cause the polling time to exceed the given limit. 

- The host keeps on hitting the busy bit until the device becomes idle or clear. 

- When the device is idle, the state is written in to the command register and also in the data out register. 

- The command ready bit is set to 1. 

- The controller sets the busy bit once it knows that the command ready bit has been set.  

- After reading from the command register, the controller carries out the required I/O operation on the device. 

- On the other hand, if the read bit has been set to one, the controller loads the device data in to the data in register. 

- This data is further read by the host. 

- Once the whole action has been completed, the command ready bit is cleared by the controller. 

- The error bit is also cleared for showing that the operation has been completed successfully. 

- At the end the busy bit is also set.

- Polling can be seen in the terms of master slave scenario where the master sends inquiring about the working status slave devices i.e., whether they are clear or engaged. 

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 Jubula - Web Functional/Regression Test Tool

Today we have around 100 tools available for functional and regression testing of the web based applications. Jubula is one among such tools and will be discussed here in detail. 

About Jubala

- This is an open source tool that is available both as a standalone application and as a part of the eclipse package.  

- The former comes with an installer that is quite easy to use and the latter one can be downloaded from an update site. 

- Jubula client can be used for viewing the actual and the expected results and also it can be used for viewing the current as well as the previous results. 

- Here, you can easily the automatic screenshots whenever an error occurs. 

- Jubula supports many applications such as:

1. Html
2. Swing
3. SWT/ RCP/ GEF and so on.

- Some features of Jubula tool have been listed below:

1. Heuristic object recognition
2. Command line client
3. Context sensitive help in client
4. Multi – user database for storing projects
5. Portability
6. Version control

- Command line has been included in this tool so as to facilitate continuous integration.

- Version control is achieved via the exports in XML format. 

- The contribution in this regard was made by BREDEX GmbH (also the developer of GUI dancer). 

- The GUIdancer was actually built up on the lines of Jubula core and offer some more features. 

- Jubula is not dependent on any platform windows, unix, linux or MAC. 

- A project by the name of ‘jubula functional testing tool’ was created as an open source project. 

- This project was a part of the eclipse technology project. 

- Other functional testing tools work up on the thing that the saving and management of the scripts is done through coding. 

Now depending up on the testing approach you are following, your test automation process may involve steps like recording, generation or straightaway writing of the code. 

What differentiates Jubala from other testing tools?

- It considers the importance of the automated acceptance tests as same as that of the project code. 

- According to Jubula, same best practices (reusability, modularity, readability etc.) should be used for creating these tests as well without requirement of any extra code. 

- Thus, the power of testing is given in the hands of the software testers and at the same time for the customers the access improves for monitoring the tests. 

- This results in a code free approach that minimizes the need for test maintenance, thus allowing the users to write the tests from their perspective. 

- If the team focuses on the software from the viewpoint of the user, it can gains a whole lot of quality info which often goes un-utilized when only JUnit tests are run.

- Jubula comes with a library of actions which is used for creating the tests. 

- You can combine the actions contained in the library using drag and drop.

- This library contains all the necessary actions that one may require for writing the tests. 

- This library is also independent of platform and application which implies that you can start writing the tests before the software is actually made available to you. 

- When you work with Jubula, you save on time since as soon as the code is committed the tests can be executed. 

- The time between the introduction of an error and catching it is reduced.

Objectives of Jubala

Jubula has got the following objectives:

1. Providing tooling for carrying out automated GUI testing on html and java based applications.
2. Specifying and maintaining a model specifications and requirements of the tests.
3. Providing API for projects so that the test scenarios can be generated, test can be executed and results can be obtained. 

What is a Silk Test Test plan? What are the types of text lines in a test plan file?

A silk test plan consists of large amounts of data as well as information based on which are the details of the plan which in turn will be used in the organization and the development of the software system or application. 

It has three basic qualities as mentioned below:

1. Well structured
2. Hierarchical
3. Ideal model

A silk test test plan constitutes of two parts which are entirely different:

1. First part consists of an outline which gives a detailed description of the all the requirements of the testing process.
2. Second part consists of a statement which establishes a relationship between the outline of the first part and 4test scripts as well as test cases which are bound to implement the requirements defined above.

What is a Silk Test Plan?

- Test plan helps in achieving a guided way for the creation as well as execution of the test cases. 

- A new test plan can be created by following the below mentioned steps:

1. Go to the file menu and then click on new option.
2. From the drop down list that follows select test plan and hit OK. You will get a test plan window. Fill in the required fields and click OK.

- This is a known fact that silk test specializes in the field of functionality as well as regression testing and has been a known product when it comes to web, java or windows based applications. 

- Silk test provides you with two ways for defining or creating the automated tests:

1. By using the record test case command for recording the actions and the verification of steps.
2. Using visual 4test scripting language by writing the test cases manually.

- Test plans in silk test are stored as ‘test plan (.pln)’ file type. 

- This file type is sometimes used for making combinations of the test scripts. 

- The basic purpose of a silk test test plan is to provide a frame work for the testing process and also for the organization and maintenance of the testing requirements. 

Benefits of using a Test Plan

Using a test plan has following benefits:

1. With test plan you have a chance to implement top down approach for defining the testing requirements, developing thoughts and refining the requirements.
2. Attributes can be assigned to individual tests or group of tests.
3. Redundancy is reduced single only actually implementing statements are allowed.
4. Can be used as a comprehensive inventory of requirements consisting of most general as well as specific requirements.

What kind of text lines are there in a test plan file?

Test plan file consists of 5 types of text lines that we have described below:

1. First type of text lines are the comments which are usually marked in green color.These types of text lines provide commentary type of information regarding the test code.
2. Group Description: This type of text lines are represented in bold black color. Furthermore, they are included so as to provide a description of a group of tests rather than describing individual tests. Usually, a test plan consists of many tests which are then grouped in to multiple levels of various groups.
3. Test Description: This type of text lines are written in blue color and are meant for showcasing the description of the individual tests only.
4. Test plan statement: This type of text lines in a test plan file provide information regarding the relations to the following elements:

a)   Test cases

b)   Link scripts

c)   Test data

d)   Closed sub test plans

e)   Include files to a test plan.

These are marked in red color.

5. Open sub plan file marker: These text lines are marked in magenta color and thus providing info regarding relations to link sub test plans with the master plan.

How do u do batch testing in WinRunner & Is it possible to do in QTP, if so explain?

WinRunner provides you the facility of executing a certain batch of the unattended tests. This feature of the winrunner has proved to be quite useful especially in the situations when a large groups of tests have to be run over night i.e., an over night run. 

How to do batch testing in WinRunner?

- A batch test can be viewed as a test consisting of a test script which holds the calls to the other tests. 

- Such call statements execute each and every test called in the list and also save the result up on execution.

- A batch test may consist of n number of tests depending up on the need and requirement of the user. 

- A batch as such just seems like a normal test but with an unusual large number of calls. 

- A batch test can be run by using the option “run in batch mode”. 

- This option is available in the run category of the general dialog box which gets invoke just before the start of the execution of the test. 

- Whenever a test is run in batch mode, all of the messages that may be displayed during the test run are suppressed by the winrunner. 

- This is done so that the winrunner is able to run a batch test unattended. 

- The execution of the batch tests is therefore different from the regular, interactive test runs where you may come across several messages popping up on the screen. 

- In batch tests, this thing is not there and so a lot of time is saved. 

- The current chain of all the called tests can be viewed at a break point in the call chain pane available for viewing in the debug viewer window. 

- After the completion of the batch test run the winrunner makes the results available in the test results window. 

- Winrunner provides you the facility of running the batch test via command line.

Is it possible to do batch testing through QTP?

- The quick test professional is the successor of the winrunner and is quite advanced and efficient in many respects as compared to the winrunner. 

- Batch testing is possible in quick test professional. 

Difference lies in the way in which the batch testing is carried out here. 

- The quick test professional facilitates the batch testing service with the help of a separate built-in tool called the test batch runner or QTP batch testing tool. 

- With this tool you can group the tests in to a number of batches which are then executed. 

- The result of this batch test run is made available in the test result viewer. 

- In quick test professional, batch wise viewing of the result is not possible. 

- Results for individual tests have to be viewed. 

- For the execution of a test batch you need to open the path of the test batch and give the run command. 

- In quick test professional, other mercury products for batch testing can also be installed and used if one is not comfortable with the in built tool of the quick test professional i.e., the test batch runner. 

- For doing this you need to follow the below mentioned sequence:

Tools menu à options à run à check the check box “allow other mercury products” à apply à ok

- Even a partial batch test is also possible! 

- You just need to deselect the tests that you want to be executed. 

- MTM or multi test manager is another mercury product using which one can carry out batch testing. 

Explain the QTP Tool interface?

The tool interface of the quick test professional is the focus of this article. The tool interface of the quick test professional consists of certain elements:

1. Title bar: This bar displays or holds the name of the test that is currently open.
2. Menu bar: This bar holds all the quick test commands that one may need often.
3. File tool bar: This bar holds all the quick test commands or tools that one may need in the management of the tests.
4. Test tool bar: This bar holds all the quick test commands or tools that may are required in the creation as well as management of the tests.
5. Debug tool bar: This bar holds all the quick test commands that may be required while debugging of the tests. Usually this bar is not displayed along with the other bars when the quick test professional is launched. If the quick test professional is not displaying the debug bar by default then you need to go to the view and select debug tool bar from the tool bars sub list.
6. Status bar: This bar displays the current status of the test that is currently under execution.
7. Action tool bar: This bar holds a list of actions using which one can view the individual details of the whole test flow or an individual test or action. Just like the debug tool bar this tool bar is also not displayed by the quick test professional by default. For displaying it along with the other bars you need to go to the view menu and select action tool bar from the sub list of the tool bars. But if you have inserted an external action or a reusable action in to your test scripts, then the quick test professional displays the action tool bar automatically.
8. Test pane: This pane consists of two tabs which enable the viewing of the test in two view modes namely: the expert view and the key word view or the tree view.
9. Test details pane: This pane holds the active screen of the quick test professional.
10. Data table: This table consists of two tabs namely: the action tab and the global tab. Both of these tabs together provide you assistance during the parameterization of your tests.
11. Debug viewer pane: This pane consists of three tabs namely, the expressions, the commands and the variables. All of these 3 tabs provide you assistance while you debug your tests. However, there is one issue with debug viewer pane which is that you can open it only when you pause the test run at a break point.

As we know that the quick test professional provides two standard views as well way to modify the test scripts namely:

1. Key word view and
2. The expert view

- It is because of these views that the quick test professional is said to possess an IDE or integrated development environment. 

- The quick test professional comes with several standard IDE features like break points etc.

- The scripting language that is used by the quick test professional i.e., the VBScript provides support for the classes but not for the other aspects of object oriented programming like inheritance, polymorphism etc. 

- It lacks some other features such as:

1. Cannot use some visual basic key words.
2. Does not have an integrated debugger.
3. No event handler
4. No forms editor

- The debugger has got a limited functionality when compared with the debuggers of java, VBA, VB.NET and so on. 

What is TSL? What 4GL is it similar too?

TSL and 4GL are two major languages that are coming in to the scenario of the present world programming languages. What do you mean by a test script actually? 

Test scripts form a set of instructions that in turn can be performed on some software system or application under test for checking whether or not the functions are giving the desired output i.e., if they are working properly or not. There are two ways via which these test scripts can be executed as mentioned below:

1. Manual testing and
2. Automated testing

In this article we shall discuss regarding the test script language or TSL and fourth generation language or 4GL. First let us start our discussion with the test script language. 

About Test Script Language

- The Test script language lies at the heart of the integrated testing environment created by the mercury interactive.

- Test script language is categorized under the category of high level languages. 

- Its usefulness is born out of the combination of the flexibility as well as the power of the conventional programming languages and functions that have been developed as a tool or a feature to be used along with the products of the mercury interactive like winrunner and test director. 

- Also, this feature of the test script language has made it to be used for the modification and programming of the sophisticated test suites. 

- The functions that the test script language provides have been grouped in to the following four categories:

1. Analog functions
2. Context sensitive functions
3. Customization functions and
4. Standard functions.

- All of the above mentioned functions do not come with all the mercury interactive products. 

- Winrunner is one such mercury interactive product which supports all of these functions. 

- Apart from just the built in functions the test script languages gives its users the provision of creating their own functions.

What are Fourth Generation Languages - 4GL?

- A fourth generation programming language needs not necessarily be a language only it can also be a programming environment. 

- The 4GLs have been developed with a certain set of design patterns in mind and are assigned a specific problem domain. 

- 4GLs were developed as a succession to the 3GLs and are known to define a higher trend of statement power as well as abstraction. 

- It was observed that the 3GL languages were quite slow and much prone to errors. 

- As a result of the efforts to overcome this problem, the 4GL languages were born and these were more focussed towards aspects like:

     1. Systems engineering

     2. Problem solving and so on.

- The fourth generation language was designed as such that they cut down on the following: 

     1. programming efforts,

     2. Time consumed in development and of course

     3. The cost of the software development.

- However, in some of the cases, a try at achieving all this resulted in an ineffective and unmanageable code. 

- A formal definition of the 4GL was given by John Capers in terms of developer productivity (i.e., in terms of function points per staff month). 

- 4GL languages are said to support 12- 20 function points per staff month. 

- The 4GLs are a subset of domain specific programming languages has been stated a number of times by some researchers. 

- 4GLs have been classified in to 4 types as stated below:

1.Table driven programming (codeless): Uses table driven algorithm. Example: power builder.

2. Report generator programming languages: Generates the required report.

3. Fourth generation environments or more ambitious 4GLs: Specialize in generation whole system from output of CASE tools.

4. Data management 4GLs: such as-

             a)   SPSS

             b)   SAS

             c)   Stata

What are all the default codes WinRunner generates when you start an application?

Automation might be quite a headache but it helps in decreasing the execution time by a great margin and in a way it saves a large number of precious man hours. Once you are done with the default installation of the winrunner you will observe that a winrunner directory has been created under programs. 

This folder consists of the following:

1. Winrunner executable
2. Uninstall winrunner
3. Soft key configuration
4. Read me
5. Fonts expert
6. Sample application folder and
7. Documentation folder etc.

The purpose of the winrunner is that it has been designed for performing functional testing and regression testing. Take a moment to study some sample application saved in the folder “sample application”. Now let us take a look at the winrunner application! 

- A tool bar is there which contains options such as new, open, save and list box for run modes namely:

1. Verify
2. Debug and
3. Update

- Plus a red button for recording purpose, green arrow for running the test scripts from line 1 and a purple line pointer for running scripts from the current line. 

- Apart from this there are start, stop and pause buttons. 

- Rest of the options on this tool bar are for debugging purpose.  

Now let us begin with the recording of a simple script! 

- You open the application software and winrunner as well. 

- Re-size both the windows such that both of them are visible to you and they do not overlap. 

- Start recording by clicking on the record button and perform some specific operations (like entering some user id and password of the start up page is login page) on the start up screen of the application. 

- After performing some 3-4 operations click on the stop button of the winrunner application and the recording will be stopped. 

- After this, the scripts can be played back and if you might have observed there is a code that the winrunner might have developed for you. 

- Now, after saving the script take a look at the code which some what looks like this:

        #startup window

        Set_window(“login”,3);

        Edit_set(“user id”,”active);

        Password_edit_set(“password”,”*****”);

        Button_press(“sign in”);

        And the code continues.

- Like the above code, the default codes are generated by the winrunner up on the start up of an application software.

- The symbol “#” marks the comments in winrunner. 

- The code may or may not contain a couple of comments. 

- The comments are inserted by the winrunner during the recording phase itself. 

- The second arguments or the numbers in the code represent the time lag between any two statements while the scripts are being recorded.

- Whenever a script is saved through winrunner, a folder by either a default name or name given by the user as the case may be is created which consists of a file by the name “script”. 

- This file consists of the default generated code in plain ASCII codes. 

- This code can be run in two modes namely the verify mode and the debug mode. 

- After this phase, comes the development mode in which the debug mode is used. 

- Finally, the verify mode is used. 

- The set_window() statement in the code lays down the focus on the window. - This helps in performing a particular function on a specific window. 

- When you type in the user id, it is identified by the winrunner and the edit_set statement is generated accordingly. 

- The next statement i.e., the  password_edit_set statement is similar to the edit_set statement, the only difference being that this field contains encrypted data and for security reasons is to be displayed as a series of asterisk “*” marks. 

When do you use Verify/Debug/Update Modes? (in Winrunner)

After you have developed the test scripts and finalized your test case, your next step is to run that particular test in order to check the behaviour of your software system or application. Whenever a test is executed using the winrunner, line by line the whole test is interpreted by the winrunner.  

As the TSL statements are interpreted line by line they are marked by an execution arrow which is visible in the left margin of the test script. As the test continues to be executed your software system or application is executed as if it is being controlled by a person. 

The winrunner provides 3 modes for the running your tests namely:

1. Verify run mode
2. Debug run mode
3. Update run mode

In this article we talk about the above mentioned three different types of winrunner run modes. 

- The first mode i.e., the verify run mode checks the application. 

- The second one i.e., the debug run mode debugs the test scripts.

- The third one i.e., the update run mode updates the expected results. 

- Only two modes i.e., the debug run mode and the verify run mode are available when you are using the winrunner run-time.

- Any one of these modes can be chosen from the list on the test tool bar. 

- The verify run mode represents the default run mode in winrunner. 

- You can either run the entire test or just a portion of it using the test and debug menu commands. 

- But always make sure all the necessary GUI map files have been loaded before you start with a context sensitive test. 

- You also have the choice of running individual tests or a group of tests using a batch test. 

- Batch test seems to be quite useful when you have very long tests to be executed and you need an overnight run. 

Now we will discuss about all the three run modes in detail one by one:

Verify run mode: 

- In this mode the current response of your software system or application is compared to the expected response by the winrunner.

- The results of this run mode are called verification results and enlist all the discrepancies that might have been observed in the current response and the expected response. 

- When the execution of the test stops, the verification results window is by default opened for the user to see. 

- As many sets as required of the verification results can be obtained. 

- However, you should always be ready with the expected results for the check points that you created earlier. 

- If there is any requirement for updating the expected results you just need to run the test in update mode.

Debug run mode: 

- This mode also helps in rooting out many of the bugs that might be residing in a test script. 

- The execution of a test in verify mode as well as debug is almost same, the only difference being in the folder in which the results are saved. 

- In this case the test results are saved in the debug folder. 

- Also, here only one set of debug results is stored and so the folder does not opens automatically for the user to view. 

- In this mode, the thing to be taken care of is that the time out variables must be changed to zero while the debugging 0of the test scripts take place.

Update run mode: 

- This mode helps in the updating of the expected results as well in the creation of a new expected results folder.

- Results for a GUI check point can also be updated and an additional set of expected results can also be created. 

When do you use Break Points? What is Toggle Break Points? How it differ from Break points?

What you got to do when you are in need of pausing a test run in between its execution? 

- Break points are used to mark such points in the test script where you want the test to be paused. 

- Break points have proved to be a very useful tool in the discovery of the flaws that might be present in a test script. 

- A break point marker marks the break point present in the test script. 

- This break point marker resides in the left margin of the test scripts.

- The test run is paused by the winrunner whenever it encounters a break point. 

- On a particular break point following tasks can be carried out:

1. The effects of the test run can be examined.
2. The current value of the variables can be viewed.
3. Any necessary changes can be made.
4. Test can be continued to further execution.

How to use Break Points?

- To continue the execution of the test after completing the task to be carried out on the break point the “run from arrow” command can be given and the test will restart from the break point. 

- Once, it gets in to the execution process again it will continue to execute until and unless it encounters another break point or till the test is complete. 

- One thing that should always be taken care of is to make sure that the winrunner is out of batch mode otherwise it won’t pause. 

- For winrunner to pause on break points, it is mandatory that it comes out of the batch mode. 

- If it is not, it is sure to ignore the break points. 

- There are 3 main uses of the break points:

1. They are used to suspend the test run at a particular point so that the state of your software system or application can be inspected.
2. They are used for monitoring the entries that are there in the watch list.
3. They are used to mark certain points throughout the test script for the stepping purpose by using the step commands.

Types of Break Points

We have two types of break points as mentioned below:

1. Break at location point: This break point makes the test to stop at some line number specified by the user in a test script and
2. Break in function point: This break point makes the test to stop whenever a functioned specified by the user is called in a loaded compiled module.

The break points that you define in a session remain active for that particular winrunner session only. Once you terminate that particular winrunner then you must redefine the break points to continue the debugging of the test script in the successive session.

Toggle Break Point and how they differ from normal break point

- Toggle break point command is used whenever you have to set a break at the location break point. 

- For doing this, you just need to move the point of insertion to that line of the test script where according to your desire the test must stop executing. 

- Now go to the debug menu and click on the option “toggle break point” or you can simply go for the button entitled toggle break point. 

- Once you have clicked on this you can observe a symbol of break point towards the left margin of the current window of the winrunner. 

- This break like other break points is also listed in the break points list.

- There is just one simple difference which is that the toggle break points automatically make use of the pass count of 0 and if some other pass count is required these break points can be easily modified.