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 1

 

1. What is Software testing?

  • Software testing is the process used to help identify the Correctness, Completeness, Security and Quality of the developed Computer Software. Software Testing is the process of executing a program or system with the intent of finding errors. A common perception of testing is that it only consists of running tests, i.e. executing the software. This is part of testing, but not all of the testing activities. Testing includes all activities before and after test execution such as:

Activities such as planning and control,

Choosing test conditions,

Designing test cases and checking results,

Evaluating exit criteria,

Reporting on the testing process and system under test

Finalizing or closure (e.g. after a test phase has been completed).

Testing also includes reviewing of documents (including source code) and static analysis.

 

2. What is the difference between system and application software?

Computer software is often divided into two categories:

  1. System software: This software includes the operating system and all utilities that enable the computer to function.

  2. Application software: These consist of programs that do real work for users.

 

3. What is the difference between Error, Bug and Defect?

  • Error: It is the Deviation from actual and the expected value.

  • Bug: It is found in the development environment before the product is shipped to the respective customer.

  • Defect: It is found in the product itself after it is shipped to the respective customer.

 

4. What is process?

  • A process is a series of steps involving activities, constraints, and resources that produce an intended output of some kind.

 

5. What are the general testing principles?

  • A number of testing principles have been suggested over the past 40 years and offer general guidelines common for all testing.

Principle 1 Testing shows presence of defects

  • Testing can show that defects are present, but cannot prove that there are no defects. Testing reduces the probability of undiscovered defects remaining in the software but, even if no defects are found, it is not a proof of correctness.

Principle 2 Exhaustive testing is impossible

  • Testing everything (all combinations of inputs and preconditions) is not feasible except for few cases.

Principle 3 Early testing

  • Testing activities should start as early as possible in the software or system development life cycle, and should be focused on defined objectives.

Principle 4 Defect clustering

  • A small number of modules contain most of the defects discovered during pre-release testing, or are responsible for the most operational failures.

Principle 5 Pesticide paradox

  • If the same tests are repeated over and over again, eventually the same set of test cases will no longer find any new defects. To overcome this "pesticide paradox", the test cases need to be regularly reviewed and revised, and new and different tests need to be written to exercise different parts of the software or system to potentially find more defects.

Principle 6 Testing is context dependent

  • Testing is done differently in different contexts. For example, safety-critical software is tested differently from an e-commerce site, same way E-commerce site are tested differently than regular Web sites.

Principle 7 Absence-of-errors fallacy

  • Finding and fixing defects does not help if the system built is unusable and does not fulfill the usersí nee

 

6. What is the difference between white box, and black box testing?

  • Black box testing is a testing strategy based solely on requirements and specifications. Black box testing requires no knowledge of internal paths, structures, or implementation of the software being tested.

  • White box testing is a testing strategy based on internal paths, code structures, and implementation of the software being tested. White box testing generally requires detailed programming skills.

 

7. What is the difference between Testing Methodology and Testing methods?

  • Testing Methodology define process, set of rules and principle which are follow by group concerned with testing the application. Here are 7 steps of testing methodology:

1. Test Requirement Analysis

2. Test Plan

3. Test Design

4. Test execute

5. Defect track

6. Test Automation

7. Test Maintain

  • Testing methods or we can say that Testing Techniques:

  • White Box Testing (Unit Testing, Integration Testing), Black Box Testing (System Testing, Functional Testing, Performance Testing>Load testing>stress testing>volume testing & Security Testing), UAT (done by user/client with actual/live data)

 

8. What is the document required to prepare during testing?

  • Normally Test engineers are responsible for any release of a project. Even the release is for staging environment or change request release or production release.

  • The minimum documents are:

Test Plan

Test Cases

Test Case Report

Bug report.

Release notes (which contains known issues).

Installation document.

 

9. What is Test data? Where we are using this in testing process? What is the importance of this data?

  • To execute test cases we should have test data. This test data should be for positive and negative testing for win runner we can get this test data from keyboard, excel sheets or from data base.

 

10. What is the difference between test case and test script?

  • Test case: is a description what data to be tested and what data to be inserted what are the actions to be done to check actual result against expected result what are the actual inputs we will use? What are the expected results? Is called test script.

  • Test Script: Is a short program written in a programming language used to test part of the functionality of the software system. A written set of steps that should be performed manually can also be called a test script; however this is more correctly called a test case.

 

Pr.Pg border                                             Next Pg