Software Testing

1. Software Testing Intro 2. What is Testing 3. Why Software Testing necessary 4. Role of Testing 5. General Testing Principles 6. Types of Software Testing 7. Load,Performance & Stress Test 8. Software Development Process 9. Project/System Life Cycle 10. Difference between terms 11. Manual V/s Automated Testing 12. Economic of Bug/Error/Fault 13. Fundamental Test Process 14. Software Testing Tools 15. HP- QTP 16. Installing QTP 9.2 17. Ex.01 Evaluating AUT 18. Ex.01 Answer 19. Ex.02 Learning AUT 20. QTP 9.2 / 10 21. QTP Window Layout 22. Test Object Model 23. Applying Test Object Model 24. Object SPY & Object Properties 25. Designing Test 26. Ex.03 Record & Running a Test 27. Ex.03 Answer 28. Saving a Test 29. Printing a Test 30. App. Record & Run Options 31. Ex.04 Sample Web Site 32. Web Record & Run options 33. Ex.05 Recording a Test 34. Working with Keyword View 35. Keyword View Description 36. Recorded Object Hierarchy 37. Ex.06 Identifying Objects 38. Ex.06 Answers 39. Keyword view columns 40. Microsoft VBScripting 41. Running VBScript 42. Msgbox Function 43. Variable 44. VBScript and QTP 45. Print statement 46. InputBox function 47. Operator Precedence 48. Cint( ) function 49. Data Types 50. VarType( ) Function 51. TypeName( ) Function 52. Cbool( ) Function 53. Cbyte( ) Function 54. Cdate( ) Function 55. CDbl( ) Function 56. Cint( ) Function 57. CLng( ) Function 58. CSng( ) Function 59. CStr( ) Function 60. If Then - End If statement 61. If Then -Else-End If statement 62. If-Elseif-Else-End If Statement 63. Len( ) Function 64. Left( ) Function 65. Right( ) Function 66. Mid( ) Function 67. Ltrim(), Rtrim(), Trim() Function 68. For-Next Statement 69. Array Function 70. ABS( ) Function 71. ASC( ) Function 72. Chr( ) Function 73. Date( ) Function 74. Now( ) Function 75. DateAdd( ) Function 76. Time( ) Function 77. DateDiff( ) Function 78. InStr( ) Function 79. InStrRev( ) Function 80. StrComp( ) Function 81. Lcase( ) Function 82. Ucase( ) Function 83. Rnd( ) & Randomizer 84. Round( ) Function 85. VBScript Procedure 86. Ex.07 QTP Logon App.Script 87. Ex.08 Synchronization 88. Ex.09 Synchronization I/O 89. Ex.10 Output Parameter 90. Ex.11 Create Input Parameter 91. Check Points 92. Ex.12 Add Standard Checkpoint 93. Ex.13 Checking Objects 94. Ex.14 Page Checkpoint 95. Ex.15 Checking Text 96. Ex.16 Checking Tables 97. Ex.17 Parameterization Test 98. Testing Interview Part1 99. Testing Interview Part2 100.Testing Interview Part3 101.Testing Interview Part4 102.Testing Interview Part5 103.Testing Interview Part6 104.Testing Interview Part7 105.Testing Interview Part8 106.Testing Interview Part9 107.Testing Interview Part10 108.Testing Interview Part11
Pr.Pg Next Pg

Designing Tests tutorials

  • You can create a test by recording the operations you perform on your application or using the keyword-driven methodology, which enables you to select keywords to indicate the operations you want to perform on your application. After you create your test, you can enhance it using checkpoints and other special testing options.

  • You can design tests using the keyword-driven methodology, step recording, or a combination of both.

  • In comparison to recording, the keyword-driven methodology generally requires a longer time-investment and at least one automation expert with a high-level of QuickTest expertise to prepare the infrastructure required for your tests, but once the infrastructure is in place, tests can be created at a more application-specific level and with a more structured design. Additionally, all the tests for a given application can be maintained more efficiently and with more flexibility than a recorded test.

  • In some cases, you may want to let QuickTest generate test steps by recording the typical processes that you perform on your application. As you navigate through your application, QuickTest graphically displays each step you perform as a row in the Keyword View. A step is anything a user does that changes the content of a page or object in your application, for example, clicking a link or typing data into an edit box. Recording may be easier for new QuickTest users or when beginning to design tests for a new application or a new feature.

  • While creating your test, you can insert checkpoints into your test. A checkpoint compares the value of an element captured when the object was saved in the object repository, with the value of the same element captured during the run session. This helps you determine whether or not your application or Web site is functioning correctly.

  • When you test your application or site, you may want to check how it performs the same operations with different data. This is called Parameterizing your test. You can supply data in the Data Table by defining environment variables and values, or you can have QuickTest generate random numbers or current user and test data.

  • After creating your initial test, you can further enhance it by adding and modifying steps in the Keyword View or Expert View.


Planning and Preparing to Create a Test

  • Before you start creating your test, you should plan it and prepare the required infrastructure. Consider the following suggestions and options:

  • Determine the functionality you want to test. Short tests that check specific functions of the application or site or complete a transaction are better than long ones that perform several tasks.

  • Decide which information you want to check during the test. A checkpoint can check for differences in the text strings, objects, and tables in your application or site.

  • Consider changing the way that QuickTest identifies specific objects. This is particularly helpful when your application contains objects that change frequently or are created using dynamic content, e.g. resultset from a database.

  • Decide how you want to organize your object repositories. For individual tests, you can work with the individual action’s object repositories, or you can use a common (shared) object repository for multiple tests. If you are new to testing, you may want to keep the default object repository per-action setting for tests. Once you feel more comfortable with the basics of test design, you may want to take advantage of the shared object repository option.

  • Find out whether an object repository containing the objects you are testing already exists. If not, create a new object repository or add objects to an existing one.

  • Determine whether you need to create any new user-defined functions or whether you should associate any existing function libraries with your test.

  • If you are recording steps, evaluate the types of events you need to record. If you need to record more or fewer events than QuickTest generally records by default, you can configure the events you want to record.

  • Consider increasing the power and flexibility of your test by replacing fixed values with parameters. When you parameterize your test, you can check how it performs the same operations with multiple sets of data, or from data stored or generated by an external source.

  • Consider using actions to streamline the testing process


Recording a Test

  • You can create the main body of a test by recording the typical processes that users perform. QuickTest records the operations you perform, displays them as steps in the Keyword View, and generates them in a script (in the Expert View).

  • Note that by default, each test includes a single action, but can include multiple actions. This chapter describes how to record a test with a single action.

  • By default, QuickTest records in the normal recording mode. If you are unable to record on an object in a given environment in the standard recording mode, or if you want to record mouse clicks and keyboard input with the exact x- and y-coordinates, you may want to record on those objects using analog or low-level recording.

Consider the following guidelines when recording a test:

  • Before you start to record, close all applications not required for the recording session.

  • If you are recording on a Web site, determine the security zone of the site. When you record on a Web browser, the browser may prompt you with security alert dialog boxes. You may choose to disable/enable these dialog boxes.

  • Decide how you want to open the application or Web browser when you record and run your test. You can choose to have QuickTest open one or more specified applications, or record and run on any application or browser that is already open.

  • Choose how you want QuickTest to record and run your test by setting global testing options in the Options dialog box and settings specific to your test in the Test Settings dialog box.



  • If you are creating a test on Web objects, you can record your test on Microsoft Internet Explorer and run it on another supported browsers (according to the guidelines specified in the QuickTest Professional). QuickTest supports running tests on the following browsers—

    1. Microsoft Internet Explorer,

    2. Netscape Browser and

    3. Mozilla Firefox.


Pr.Pg border                                              Next Pg