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. Intro.to 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 7

 

61. Which test cases are not to be automated?

  • All the test cases which are related to a feature of the product, that keeps on changing (there are always some or the other enhancements in it). Frequent enhancements may change the UI, add/remove few controls. Hence such cases, if automated, would involve lot of a intendance

 

62. Explain VSS (Virtual Source Safe)?

  • After completion of all phages from development side developer store the code in development folder of VSS, Testing team copying code from that folder to testing folder, after completing above phages from testing, testers put the build in base line folder. It is version control Tool mainly useful to developer, to storing code and maintains version Copying a code from VSS By developer is called CHECK-IN Upload the code in to VSS is called CHECK-OUT.

 

63. Who will assign severity & priority?

  • The tester/developer should give the priority based on severity of the bug

  • Severity means: is the impact of the bug on the application i.e. seriousness of the bug interims of the functionality.

  • Priority means: is how soon it should get fixed i.e. importance of the bug interims of customer

 

64. What is the Difference between Stub Testing and Driver Testing?

  • Stub testing: In top down approach, a core module is developed. To test that core module, small dummy modules are used. So stubs are small dummy modules that test the core module.

  • Driver testing: In bottom up approach, small modules are developed. To test them a dummy core module called driver is developed.

 

65. What is a software review?

  • A software review can be defined as a filter for the software engineering process. The purpose of any review is to discover errors in the analysis, design, and coding, testing and implementation phases of the softwaredevelopment cycle. The other purpose of a review is to see whether procedures are applied uniformly and in a manageable manner.

 

66. What is a “Good Tester”?

  • Is one who tries to break the developers software and in a position to venture the bugs. So that at least 80% bugs free software can deliver.

 

67. What is the difference between Retesting and Data Driven Testing?

  • Retesting: It is manual process in which application will be tested with entire new set of data.

  • Data Driven Testing (DDT): It is a Automated testing process in which application is tested with multiple test dated is very easy procedure than retesting because the tester should sit and need to give different new inputs manually from front end and it is very tedious and boring procedure.

 

68. How do you test web application?

  • Web application testing: Web application should have the following features like

1. Attractive User Interface (logos, fonts, alignment)

2. High Usability options

3. Security features (if it has login feature)

4. Database (back end).

5. Performance (appearing speed of the application on client system)

6. Able to work on different Browsers (Browser compatibility), O.S compatibility (technically called as portability)

7. Broken link testing………etc

  • So we need to follow out the following test strategy:

1. Functionality Testing

2. Performance Testing (Load, volume, Stress, Scalability)

3. Usability Testing

4. User Interface Testing (colors, fonts, alignments…)

5. Security Testing

6. Browser compatibility Testing (different versions and different browser)

7. Broken link and Navigation Testing

8. Database (back end) Testing (data integrity)

9. Portability testing (Multi O.s Support)….etc

 

69. What are the client side scripting languages and server side scripting languages?

  • Client side scripting languages are useful to validate the inputs or user actions from user side or client side. Client side scripting languages are: Javascript, VbScript, PHP…etc.

  • Client side scripting is good because it won’t send the unwanted input’s to server for validation. From front-end it self it validated the user inputs and restricts the user activities and guides him.

  • Server side Scripting languages are to validate the inputs at server side. Server side Scripting languages are: Perl, JSP, ASP, and PHP etc…These scripting languages provide security for the application and also provides dynamic nature to web or client server application.

 

70. What is positive and negative testing? Explain with example?

  • Positive Testing: - testing the system by giving the valid data.

  • Negative Testing: - testing the system by giving the Invalid data.

  • Example: Application contains a textbox and as per the user’s Requirements the textbox should accept only Strings. By providing only String as input data to the textbox & to check whether its working properly or not means it is Positive Testing. If giving the input other than String means it is negative Testing.

 

Pr.Pg border                                              Next Pg