Start running our test. Click Run or choose Test > Run. The Run dialog box opens. Select New run results folder. Accept the default results folder name. Click OK to close the Run dialog box.

Select File > Save or click the Save button. > The Save dialog box opens to the Tests folder. > Create a folder which you want to save to, select it, and click Open. > Type our test name in the File name field. > Confirm that Save Active Screen files is selected. Click Save. > our test name is displayed in the title bar of the main QuickTest window.

AS we are saying that the all images are as push button than we can check the property enabled or disabled. If we are not able to find that property than go to object repository for that objecct and click on add remove to add the available properties to that object. Let me know if that works. And if we take it as image than we need to check visible or invisible property tht also might help you are there are no enable or disable properties for the image object.

> Record or click the Record button. When the Record and Run Settings dialog box opens to do this ; > In the Web tab, select Open the following browser when a record or run session begins. > In the Windows Applications tab, confirm that Record and run on these applications (opened on session start) is selected, and that there are no applications listed.

Here are tools to check this. Compuware DevPartner can help we test our application for Memory leaks if the application is complex. Also depending upon the OS on which we need to check for memory leaks we need to select the tool.

If the initial testing approach was manual testing, then the regression testing is usually performed manually. Conversely, if the initial testing approach was automated testing, then the regression testing is usually performed by automated testing.

obj_ChkDesc.remove html tag would delete the html tag property from the collection.

Testing in itself cannot ensure the quality of software. All testing can do is give you a certain level of assurance (confidence) in the software. On its own, the only thing that testing proves is that under specific controlled conditions, the software functioned as expected by the test cases executed.

The format for all test cases could be something like this > test cases for GUI > +ve test cases for login. > -ve test cases for login. in the -ve scenario : we should include boundary analysis to create test cases ,Value Analysis. Equivalence Classes,Positive and Negative test cases) plus cross-site scripting and SQL injection. SQL injection is especially high-risk for login pages.

In credit card testing the following validations are considered > Testing the 4-DBC (Digit batch code) for its uniqueness (present on right corner of credit card) > The message formats in which the data is sent > LUHN testing > Network response > Terminal validations