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 10


91. How can you know bug is reproducible or not?

  • A bug is reproducible if we can reproduce it, if we cannot reproduce it, it is not reproducible in which case we will do further testing around it and if we cannot see it we will close it, and just hope it would never come back ever again.


92. How is traceability of bug follow?

  • The traceability of bug can be followed in so many ways.

1. Mapping the functional requirement scenarios(FS Doc) - test cases (ID) - Failed test cases(Bugs)

2. Mapping between requirements (RS Doc) - Test case (ID) - Failed test cases.

3. Mapping between test plans (TP Doc) - test case (ID) - failed test cases.

4. Mapping between business requirements (BR Doc) - test cases (ID) - Failed test cases.

5. Mapping between high level designs (Design Doc) - test cases (ID) - Failed test cases.

  • Usually the traceability matrix is mapping between the requirements, client requirements, function specification, test plan and test cases.


93. What is defect life cycle in manual testing?

Defect Life Cycle:

  • Defect detection

  • Reproduce the defects

  • Assign the bug to the developer

  • Bug fixing

  • Bug resolution

  • Regression


94. What is difference between bug resolution meeting and bug review committee? Who are the participants in bug resolution meeting and bug review committee?

  • Bug Resolution meeting: It is conducted in presence of test lead and developers where developer gives his comment whether to correct the bug at this time or later and test leader accepts or rejects developer comments and even they decide what methods should be chosen correct the error so that in regression test no bug should be reported and it should not effect other application.

  • Bug Review committee: It is often conducted by test lead, project managers in the presence of client, where they decide as to what errors should be considered as bugs and what severity level it should be treated as.


95. What are the different types of bugs we normally see in any of the project?

  • User interface defects

  • Boundary related defects

  • Error handling defects

  • Calculation defects

  • Improper service levels

  • Interpreting data defects

  • Race condition (comparability and inter system defects)

  • Load conditions (Memory leakages under load)

  • Hardware failures

  • Source bugs


96. What is a difference between a Defect and an enhancement?

  • Defect: Defect is the problem or error found in the application while testing which is unnecessary or which my hindrant to the other functions of the application.

  • Enhancement: Itís the additional feature or functionality found and added to the application as desired by the end user/real word customer or tester during the testing process. Enhancement can be applied when the application's basic functionality is proper. Where as when the defect is found the program can not be considered as proper and up to the mark until its fixed.

  • Enhancement is done to improve the quality of the software where as Defect is removed or repair to maintain the quality of the software.


97. What is Red Box testing? What is Yellow Box testing? What is Grey Box testing?

  • Grey box testing: is the combination of white box testing & black box testing.

  • Yellow box testing: It is a message level testing. Simply yellow box testing is checking against the warning messages. Whether the system properly throwing the warning messages or not? is testing the for warning messages

  • Red box testing: User / Client can apply any techniques to accept the project. They will apply white box or grey box or black box for accepting the project. So we are calling the user acceptance testing as a red box testing. Also networking, peripherals testing and protocol testing called red box testing.


98. What is log sheet? And what are the components in it?

  • A log sheet is generally a defect report. Server logs are also attached to the defect, for the developers to check, what is the behavior of the application, request and response of the remote server when the defect has occurred.By reading that log sheet, a programmer or developer can understand why that defect has occurred.This log sheet consists of lines of code according to the series of events that made the defect to occur.


99. What is Multi Unit testing?

  • Each and every project consists of set of modules. After completion of all modules development those are integrated as a system. After that we perform the system testing. Here we are conducting testing on each and every module that is called as unit testing. When ever two modules (sometimes call it as unit) are in testing process then we say that multi unit testing is going on for a particular project.


100. What are the three stake holders in testing?

  • Stake holder means who are directly or indirectly involved in the project.

1. Client

2. Testing Team

3. Development Team


Pr.Pg border                                              Next Pg