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

Software Testing Interview Questions and Answers Part 6


51. How do you review test case? Type of Review…

  • Types of reviewing test cases depend upon company standards, viz..,

  • Peer review, team lead review, project manager review. Sometimes client may also review the test cases reg what is approach following for project


52. In which way tester get Build a, Build B, Build Z of an application, just explains the process?

  • After preparation of test cases project manager will release software release note in that Document there will be URL path of the website link from that we will receive the build In case of web server projects, you will be provided with an URL or a 92.168. ***. *** (Web address) which will help you access the project using a browser from your system.

  • In case of Client server, the build is placed in the VSS (Configuration tool) which will help you get the .exe downloaded to your computer.


53. What are the advantages of waterfall model?

  • The various advantages of the waterfall model include:

    1. It is a linear model.

    2. It is a segmental model.

    3. It is systematic and sequential.

    4. It is a simple one.

    5. It has proper documentation.


54. What are the contents of test report?

  • There are two documents, which should be prepared at particular phase.

1. Test Results document.

2. Test Report document.

  • Test Results doc will be prepared at the phase of each type of testing like FULL FUNCTIONAL TEST PASS, REGRESSION TEST PASS, and SANITY TEST PASS etc…Test case execution against the application. Once you prepared this doc, we will send the doc to our TL and PM. By seeing the Test Results doc, TL will come to know the coverage part of the test case. Here are the contents used in the Test Results doc:

1. Build No

2. Version Name

3. Client OS

4. Feature set

5. Main Feature

6. Defined Test cases on each feature.

7. QA engineer Name

8. Test e-cases executed. (Includes pass and fail)

9. Test cases on HOLD (Includes blocking test cases and deferred Test cases)

10. Coverage Report (Which includes the coverage ratings in %, like % of test cases covered, % of test cases failed)

  • Coming to Test report, generally we will prepare Test report, once we rolled out the product to our client. This document will be prepared by TL and delivered to the client. Mainly, this document describes the what we have done in the project, achievements we have reached, our Learning’s in throughout the project etc…

  • The other name for Test report is Project Closure Report and we will summarize the all the activities, which have taken place in throughout the project. Here are the contents covered in the Test Report:

1. Test Environment (Should be covered the OS, Application or web servers, Machine names, Database, etc…)

2. Test Methods(Types of Tests, we have done in the project like Functional Testing, Platform Testing, regression Testing, etc..

3. Major areas Covered.

4. Bug Tracking Details. (Includes inflow and outflow of the bus in our delivered project)

5. Work schedule (When we start the testing and we finished)

6. Defect Analysis

a. Defects logged in different types of tests like Functional Test, regression Test as per area wised.

b. State of the Defects at end of the Test cycle.

c. Root cause analysis for the bugs marked as NOT A BUG.

7. QA observations or learning’s thought the life cycle.


55. What are the types of attributes?

  1. Simple Attribute

  2. Composite Attribute

  3. Single Valued Attribute

  4. Multivalued Attribute

  5. Derived Attribute


56. Write high level test cases?

  • Write all the test cases under high level TC, which can be covered the main functionalities like Creation, edition, deletion, etc….as per prescribed in the screen.

  • Write all the test cases under low level TC, which can be covered the screen, like input fields are displayed as per the requirements, buttons are enabled or disabled, and test case for low priority functionalities.

  • Example: a screen contains two edit boxes login and password and a put buttons OK and Reset and check box for the label “Remember my password”. Now let us write high level TC and low level test cases.


1. Verify that User is able to login with valid login and valid password.

2. Verify that User is not able to login with invalid login and valid password.


3. Verify that Reset button clears the filled screen.

4. Verify that a pop up message is displayed for blank login.



1. Verify that after launching the URL of the application below fields are displays in the screen.

2. Login Name 3. Password. 4. OK BUTTON 5. RESET button etc.

3. Check box, provided for the label “remember my password” is unchecked.

4. Verify that OK button should be disabled before selecting login and password fields.

5. Verify that OK button should we enabled after selecting login and password.

6. Verify that User is able to check the check box, provided for the label “remember my password”.


  • In this way, we can categories all the test cases under HIGH LEVEL and LOW LEVEL.


57. What is test scenario?

  • Test scenario will be framed on basis of the requirement, which need to be checked. For that, we will frame set of test cases, in other terms, we can say all the conditions, which can be determined the testing coverage against business requirement.

  • Please see the below example, which is exactly matched to my explanation.

  • As we know all most all the application are having login screen, which contains login name and password. Here is the test scenario for login screen.

  • Scenario: USER’S LOGIN

Conditions to be checked to test the above scenario:

1. Test login field and Password fields individually.

2. Try to login with valid login and valid password.

3. Try to login with invalid login and valid password. Etc


58. What are the advantages of black box testing?

The advantages of this type of testing include:

  • The test is unbiased because the designer and the tester are independent of each other.

  • The tester does not need knowledge of any specific programming languages.

  • The test is done from the point-of-view of the user, not the designer.

  • Test cases can be designed as soon as the specifications are complete.


59. What is build duration?

  • It is a tine gap between old version build and new version build in new version build some new extra features are added.


60. What is test deliverables?

  • Test deliverables are nothing but documents preparing after testing like test plan document test case template bug report template. Test deliverables will be delivered to the client not only for the completed activities, but also for the activities, which we are implementing for the better productivity. (As per the company’s standards). Here are some of the Test deliverables:

1. QA Test Plan

2. Test case Docs

3. QA Test plan, if we are using Automation.

4. Automation scripts

5. QA Coverage Matrix and defect matrix.

6. Traceability Matrix

7. Test Results doc

8. QA Schedule doc (describes the deadlines)

9. Test Report or Project Closure Report. (Prepared once we rolled out the project to client)

10. Weekly status report (sent by PM to the client)

11. Release Notes.


Pr.Pg border                                              Next Pg