Test Conditons: Creating and Calling user define funtion 2b. Go to Tools menu --> General Options |
Blog for QuickTest Pro (QTP) posts for experts and contains frameworks and scripts
Creating and Calling user define funtion
Diff between Image & Bit map Check point
Image checkpoints enable you to check the properties of a Web image. You can check an area of a Web page or application as a bitmap. While creating a test or component, you specify the area you want to check by selecting an object. You can check an entire object or any area within an object. QuickTest captures the specified object as a bitmap, and inserts a checkpoint in the test or component. You can also choose to save only the selected area of the object with your test or component in order to save disk Space For example, suppose you have a Web site that can display a map of a city the user specifies. The map has control keys for zooming. You can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, you can check that the map zooms in correctly.
You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded).
Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.
You can create bitmap checkpoints for all supported testing environments (as long as the appropriate add-ins are loaded).
Note: The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.
How many ways we can parameterize data in QTP?
There are four types of parameters:
Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test.
Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, QuickTest uses a different value from the Data Table.
Environment variable parameters enable you to use variable values from other sources during the run session. These may be values you supply, or values that QuickTest generates for you based on conditions and options you choose.
Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have QuickTest generate a random number and insert it in a number of tickets edit field.
Test, action or component parameters enable you to use values passed from your test or component, or values from other actions in your test.
Data Table parameters enable you to create a data-driven test (or action) that runs several times using the data you supply. In each repetition, or iteration, QuickTest uses a different value from the Data Table.
Environment variable parameters enable you to use variable values from other sources during the run session. These may be values you supply, or values that QuickTest generates for you based on conditions and options you choose.
Random number parameters enable you to insert random numbers as values in your test or component. For example, to check how your application handles small and large ticket orders, you can have QuickTest generate a random number and insert it in a number of tickets edit field.
Choosing a test automation framework
There are lot of resources on the internet explaining different types of automation frameworks and how to go about selecting one of them those suites your environment.
Below are few links which provide you solid understanding of the software test automation frameworks.
http://www.ibm.com/developerworks/rational/library/591.html
www.research.ibm.com/journal/sj/411/rankin.pdf
http://www.wilsonmar.com/WRSAFS/Docs/CHAPTER1.doc
http://en.wikipedia.org/wiki/Test_Automation_Framework
www.michaeldkelly.com/images/Choosing_a_Test_Automation_Framework.PDF
www.logigear.com/resources/articles_lg/Automation_Framework.pdf
Below are few links which provide you solid understanding of the software test automation frameworks.
http://www.ibm.com/developerworks/rational/library/591.html
www.research.ibm.com/journal/sj/411/rankin.pdf
http://www.wilsonmar.com/WRSAFS/Docs/CHAPTER1.doc
http://en.wikipedia.org/wiki/Test_Automation_Framework
www.michaeldkelly.com/images/Choosing_a_Test_Automation_Framework.PDF
www.logigear.com/resources/articles_lg/Automation_Framework.pdf
Subscribe to:
Posts (Atom)