T4Tutorials .PK

Software Testing MCQs

Q1. Software testing is:
(A) Process of evaluating software to detect defects
(B) Writing code only
(C) Hardware installation
(D) UI design
Answer: (A) Process of evaluating software to detect defects

Q2. The main objective of software testing is:
(A) Ensure software meets requirements and works correctly
(B) Install hardware
(C) Design UI only
(D) Database setup
Answer: (A) Ensure software meets requirements and works correctly

Q3. Verification in software testing means:
(A) Checking if software complies with specifications
(B) Running the program
(C) UI design
(D) Hardware setup
Answer: (A) Checking if software complies with specifications

Q4. Validation in software testing means:
(A) Checking if software meets user needs
(B) Checking syntax only
(C) Database setup
(D) UI screens only
Answer: (A) Checking if software meets user needs

Q5. Unit testing focuses on:
(A) Individual code modules
(B) Entire system
(C) Database only
(D) UI only
Answer: (A) Individual code modules

Q6. Integration testing focuses on:
(A) Interactions between modules
(B) Single module only
(C) Hardware only
(D) UI only
Answer: (A) Interactions between modules

Q7. System testing tests:
(A) Complete integrated system
(B) Single module only
(C) Hardware only
(D) UI screens only
Answer: (A) Complete integrated system

Q8. Acceptance testing is performed:
(A) To verify software meets user requirements
(B) During coding only
(C) UI layout only
(D) Hardware setup
Answer: (A) To verify software meets user requirements

Q9. Smoke testing is:
(A) Preliminary testing to check basic functionality
(B) Database testing
(C) UI testing only
(D) Hardware setup
Answer: (A) Preliminary testing to check basic functionality

Q10. Sanity testing ensures:
(A) Specific functionality works after minor changes
(B) Complete system
(C) Hardware only
(D) UI only
Answer: (A) Specific functionality works after minor changes

Q11. Regression testing ensures:
(A) New changes do not break existing functionality
(B) Hardware only
(C) UI screens only
(D) Database only
Answer: (A) New changes do not break existing functionality

Q12. Functional testing checks:
(A) Software functions against requirements
(B) Hardware setup
(C) UI layout only
(D) Database only
Answer: (A) Software functions against requirements

Q13. Non-functional testing checks:
(A) Performance, usability, and reliability
(B) UI screens only
(C) Database only
(D) Hardware only
Answer: (A) Performance, usability, and reliability

Q14. Black box testing focuses on:
(A) Testing without knowledge of internal code
(B) Code structure
(C) Database only
(D) Hardware setup
Answer: (A) Testing without knowledge of internal code

Q15. White box testing focuses on:
(A) Testing internal code structure
(B) UI only
(C) Database only
(D) Hardware only
Answer: (A) Testing internal code structure

Q16. Gray box testing is:
(A) Combination of black box and white box testing
(B) UI testing only
(C) Database only
(D) Hardware only
Answer: (A) Combination of black box and white box testing

Q17. Static testing involves:
(A) Reviewing code or documents without execution
(B) Running program
(C) UI only
(D) Hardware only
Answer: (A) Reviewing code or documents without execution

Q18. Dynamic testing involves:
(A) Executing code to find defects
(B) Reviewing documents only
(C) UI only
(D) Database only
Answer: (A) Executing code to find defects

Q19. Test plan includes:
(A) Scope, approach, resources, and schedule of testing
(B) UI layout only
(C) Hardware setup only
(D) Database tables only
Answer: (A) Scope, approach, resources, and schedule of testing

Q20. Test case specifies:
(A) Input, expected output, and execution conditions
(B) UI colors only
(C) Database only
(D) Hardware setup
Answer: (A) Input, expected output, and execution conditions

Q21. Test suite is:
(A) Collection of test cases for a particular objective
(B) Database tables
(C) UI screens only
(D) Hardware only
Answer: (A) Collection of test cases for a particular objective

Q22. Boundary value testing focuses on:
(A) Values at the edges of input domains
(B) Database keys only
(C) UI layout only
(D) Hardware only
Answer: (A) Values at the edges of input domains

Q23. Equivalence partitioning divides input data into:
(A) Valid and invalid partitions
(B) Database tables only
(C) UI only
(D) Hardware only
Answer: (A) Valid and invalid partitions

Q24. Error guessing is based on:
(A) Tester experience to anticipate defects
(B) Random selection only
(C) Database only
(D) UI only
Answer: (A) Tester experience to anticipate defects

Q25. Load testing evaluates:
(A) System behavior under expected load
(B) UI screens only
(C) Hardware setup only
(D) Database only
Answer: (A) System behavior under expected load

Q26. Stress testing evaluates:
(A) System behavior under extreme load
(B) Normal load only
(C) UI only
(D) Database only
Answer: (A) System behavior under extreme load

Q27. Performance testing ensures:
(A) Software meets performance criteria
(B) Hardware installation
(C) Database only
(D) UI layout only
Answer: (A) Software meets performance criteria

Q28. Usability testing evaluates:
(A) Ease of use for end-users
(B) Hardware only
(C) Database only
(D) Coding errors only
Answer: (A) Ease of use for end-users

Q29. Security testing checks:
(A) Software protection against threats and vulnerabilities
(B) UI layout only
(C) Database only
(D) Hardware only
Answer: (A) Software protection against threats and vulnerabilities

Q30. Compatibility testing ensures:
(A) Software works across different platforms and environments
(B) UI screens only
(C) Database only
(D) Hardware only
Answer: (A) Software works across different platforms and environments

Q31. Alpha testing is:
(A) Performed by developers before release
(B) End-users testing only
(C) Database testing only
(D) Hardware testing only
Answer: (A) Performed by developers before release

Q32. Beta testing is:
(A) Performed by end-users before final release
(B) Developers only
(C) Hardware testing only
(D) Database testing only
Answer: (A) Performed by end-users before final release

Q33. Automated testing reduces:
(A) Manual effort and improves repeatability
(B) Hardware efficiency
(C) UI only
(D) Database only
Answer: (A) Manual effort and improves repeatability

Q34. Selenium is used for:
(A) Automated web application testing
(B) Database setup
(C) Hardware testing only
(D) UI design only
Answer: (A) Automated web application testing

Q35. JUnit is used for:
(A) Unit testing in Java applications
(B) UI layout only
(C) Hardware testing only
(D) Database testing
Answer: (A) Unit testing in Java applications

Q36. Test coverage measures:
(A) Percentage of code exercised by tests
(B) UI screens only
(C) Database only
(D) Hardware only
Answer: (A) Percentage of code exercised by tests

Q37. Defect density is:
(A) Number of defects per unit size of software
(B) Hardware failure rate
(C) UI error rate only
(D) Database error rate
Answer: (A) Number of defects per unit size of software

Q38. Severity of a defect indicates:
(A) Impact on system functionality
(B) UI color only
(C) Database setup
(D) Hardware only
Answer: (A) Impact on system functionality

Q39. Priority of a defect indicates:
(A) Order in which defect should be fixed
(B) Database table only
(C) UI screens only
(D) Hardware only
Answer: (A) Order in which defect should be fixed

Q40. Static code analysis detects:
(A) Defects without executing the program
(B) Only UI errors
(C) Hardware issues only
(D) Database errors only
Answer: (A) Defects without executing the program

Q41. Dynamic code analysis detects:
(A) Defects during program execution
(B) Hardware only
(C) UI only
(D) Database only
Answer: (A) Defects during program execution

Q42. Pairwise testing is used to:
(A) Test all possible combinations of inputs
(B) Database only
(C) UI screens only
(D) Hardware only
Answer: (A) Test all possible combinations of inputs

Q43. Boundary testing is a type of:
(A) Black box testing
(B) White box testing
(C) Database only
(D) Hardware only
Answer: (A) Black box testing

Q44. Statement coverage ensures:
(A) Every statement in code is executed at least once
(B) UI screens only
(C) Database only
(D) Hardware only
Answer: (A) Every statement in code is executed at least once

Q45. Branch coverage ensures:
(A) Every branch in decision statements is executed
(B) Database only
(C) UI only
(D) Hardware only
Answer: (A) Every branch in decision statements is executed

Q46. Condition coverage ensures:
(A) Every boolean sub-expression is evaluated to true and false
(B) UI only
(C) Database only
(D) Hardware only
Answer: (A) Every boolean sub-expression is evaluated to true and false

Q47. Mutation testing is used to:
(A) Evaluate test effectiveness by introducing faults
(B) Database only
(C) UI only
(D) Hardware only
Answer: (A) Evaluate test effectiveness by introducing faults

Q48. Exploratory testing relies on:
(A) Tester experience and creativity
(B) Predefined test cases only
(C) Hardware only
(D) Database only
Answer: (A) Tester experience and creativity

Q49. Monkey testing is:
(A) Random input testing
(B) Systematic testing only
(C) Database only
(D) Hardware only
Answer: (A) Random input testing

Q50. End-to-end testing ensures:
(A) Complete workflow works as expected
(B) Single module only
(C) Database only
(D) UI screens only
Answer: (A) Complete workflow works as expectedQ51. Alpha testing is performed:
(A) In-house by developers before release to users
(B) By end-users only
(C) On database tables only
(D) On UI screens only
Answer: (A) In-house by developers before release to users

Q52. Beta testing is performed:
(A) By selected end-users before final release
(B) By developers only
(C) On hardware only
(D) On UI only
Answer: (A) By selected end-users before final release

Q53. Load testing measures:
(A) System behavior under expected workload
(B) Only UI performance
(C) Database capacity
(D) Hardware speed only
Answer: (A) System behavior under expected workload

Q54. Stress testing measures:
(A) System behavior under extreme conditions
(B) Normal load only
(C) UI layout only
(D) Database only
Answer: (A) System behavior under extreme conditions

Q55. Spike testing evaluates:
(A) System behavior under sudden large load
(B) Regular performance
(C) UI only
(D) Database only
Answer: (A) System behavior under sudden large load

Q56. Endurance testing ensures:
(A) System stability over prolonged use
(B) Short-term functionality
(C) UI layout only
(D) Hardware only
Answer: (A) System stability over prolonged use

Q57. Usability testing evaluates:
(A) Ease of use and user experience
(B) Hardware efficiency
(C) Database only
(D) Code only
Answer: (A) Ease of use and user experience

Q58. Security testing checks for:
(A) Vulnerabilities and threats
(B) UI layout only
(C) Database only
(D) Hardware only
Answer: (A) Vulnerabilities and threats

Q59. Penetration testing is:
(A) Simulated attack to find security weaknesses
(B) Normal usage testing
(C) Database only
(D) UI only
Answer: (A) Simulated attack to find security weaknesses

Q60. Compatibility testing ensures:
(A) Software works on multiple platforms, browsers, and devices
(B) UI screens only
(C) Database only
(D) Hardware only
Answer: (A) Software works on multiple platforms, browsers, and devices

Q61. Recovery testing evaluates:
(A) System behavior after failure or crash
(B) Normal execution only
(C) Database only
(D) UI screens only
Answer: (A) System behavior after failure or crash

Q62. Installation testing checks:
(A) Software installs and uninstalls correctly
(B) Hardware setup only
(C) Database only
(D) UI only
Answer: (A) Software installs and uninstalls correctly

Q63. Configuration testing ensures:
(A) Software works under different configurations
(B) Single setup only
(C) Database only
(D) Hardware only
Answer: (A) Software works under different configurations

Q64. Regression testing is performed:
(A) After code changes to ensure existing functionality is not broken
(B) Before writing code
(C) UI only
(D) Hardware only
Answer: (A) After code changes to ensure existing functionality is not broken

Q65. Smoke testing is also called:
(A) Build verification testing
(B) Sanity testing only
(C) UI testing only
(D) Database only
Answer: (A) Build verification testing

Q66. Sanity testing is performed:
(A) To verify specific functionality after minor changes
(B) Full system testing
(C) Hardware only
(D) UI only
Answer: (A) To verify specific functionality after minor changes

Q67. Black box testing does not consider:
(A) Internal code structure
(B) Functionality
(C) Input/output
(D) Requirements
Answer: (A) Internal code structure

Q68. White box testing requires knowledge of:
(A) Internal code logic
(B) Only UI layout
(C) Database tables
(D) Hardware setup
Answer: (A) Internal code logic

Q69. Gray box testing combines:
(A) Black box and white box testing approaches
(B) Only UI testing
(C) Database only
(D) Hardware only
Answer: (A) Black box and white box testing approaches

Q70. Static testing includes:
(A) Reviews, inspections, and walkthroughs without executing code
(B) Running the program
(C) UI only
(D) Hardware only
Answer: (A) Reviews, inspections, and walkthroughs without executing code

Q71. Dynamic testing includes:
(A) Executing code to find defects
(B) Only code review
(C) UI only
(D) Database only
Answer: (A) Executing code to find defects

Q72. Test case consists of:
(A) Input, expected output, and execution conditions
(B) Only UI elements
(C) Database table design
(D) Hardware setup only
Answer: (A) Input, expected output, and execution conditions

Q73. Test suite is:
(A) Collection of related test cases
(B) Single test case
(C) UI only
(D) Hardware only
Answer: (A) Collection of related test cases

Q74. Equivalence partitioning divides input data into:
(A) Classes of valid and invalid input
(B) Random input only
(C) UI screens only
(D) Database only
Answer: (A) Classes of valid and invalid input

Q75. Boundary value analysis focuses on:
(A) Input values at the edges of input domain
(B) Normal input only
(C) UI only
(D) Database only
Answer: (A) Input values at the edges of input domain

Q76. Error guessing relies on:
(A) Tester experience to anticipate defects
(B) Random input only
(C) Database only
(D) Hardware only
Answer: (A) Tester experience to anticipate defects

Q77. Statement coverage ensures:
(A) Each statement is executed at least once
(B) Branch coverage only
(C) UI only
(D) Database only
Answer: (A) Each statement is executed at least once

Q78. Branch coverage ensures:
(A) Every decision branch is executed
(B) Only statements
(C) UI only
(D) Database only
Answer: (A) Every decision branch is executed

Q79. Condition coverage ensures:
(A) Every boolean sub-condition is true and false
(B) UI only
(C) Database only
(D) Hardware only
Answer: (A) Every boolean sub-condition is true and false

Q80. Mutation testing is performed to:
(A) Evaluate effectiveness of test cases by introducing faults
(B) Normal testing only
(C) UI only
(D) Database only
Answer: (A) Evaluate effectiveness of test cases by introducing faults

Q81. Exploratory testing relies on:
(A) Tester knowledge and creativity
(B) Predefined test cases only
(C) UI only
(D) Hardware only
Answer: (A) Tester knowledge and creativity

Q82. Monkey testing involves:
(A) Random input testing
(B) Systematic testing only
(C) Database only
(D) UI only
Answer: (A) Random input testing

Q83. End-to-end testing checks:
(A) Complete system workflow from start to finish
(B) Single module only
(C) Database only
(D) UI screens only
Answer: (A) Complete system workflow from start to finish

Q84. Load testing tools include:
(A) JMeter, LoadRunner
(B) Selenium only
(C) UI layout only
(D) Database only
Answer: (A) JMeter, LoadRunner

Q85. Security testing tools include:
(A) OWASP ZAP, Burp Suite
(B) JMeter only
(C) UI only
(D) Hardware only
Answer: (A) OWASP ZAP, Burp Suite

Q86. Code coverage measures:
(A) How much code is exercised by tests
(B) Database only
(C) UI only
(D) Hardware only
Answer: (A) How much code is exercised by tests

Q87. Defect density is:
(A) Number of defects per unit size of software
(B) Hardware failure rate
(C) UI errors only
(D) Database errors only
Answer: (A) Number of defects per unit size of software

Q88. Severity of defect indicates:
(A) Impact on system functionality
(B) Hardware only
(C) UI screens only
(D) Database only
Answer: (A) Impact on system functionality

Q89. Priority of defect indicates:
(A) Order in which defect should be fixed
(B) UI screens only
(C) Hardware only
(D) Database only
Answer: (A) Order in which defect should be fixed

Q90. Automated testing reduces:
(A) Manual effort and improves consistency
(B) Hardware only
(C) UI only
(D) Database only
Answer: (A) Manual effort and improves consistency

Q91. Selenium is used for:
(A) Automated web application testing
(B) Database only
(C) UI layout only
(D) Hardware only
Answer: (A) Automated web application testing

Q92. JUnit is used for:
(A) Unit testing in Java applications
(B) UI only
(C) Database only
(D) Hardware only
Answer: (A) Unit testing in Java applications

Q93. Continuous integration tools include:
(A) Jenkins, Travis CI, CircleCI
(B) Selenium only
(C) UI only
(D) Hardware only
Answer: (A) Jenkins, Travis CI, CircleCI

Q94. Regression testing ensures:
(A) New changes do not break existing functionality
(B) UI only
(C) Database only
(D) Hardware only
Answer: (A) New changes do not break existing functionality

Q95. Test-driven development (TDD) involves:
(A) Writing tests before code implementation
(B) Writing code first
(C) Database only
(D) UI only
Answer: (A) Writing tests before code implementation

Q96. Recovery testing ensures:
(A) System recovers after failure
(B) Normal execution only
(C) UI only
(D) Hardware only
Answer: (A) System recovers after failure

Q97. Configuration testing ensures:
(A) Software works on different setups
(B) Single configuration only
(C) Database only
(D) UI only
Answer: (A) Software works on different setups

Q98. Installation testing ensures:
(A) Software installs/uninstalls correctly
(B) Hardware only
(C) Database only
(D) UI only
Answer: (A) Software installs/uninstalls correctly

Q99. Monkey testing is also known as:
(A) Random testing
(B) Exploratory testing only
(C) Database only
(D) UI only
Answer: (A) Random testing

Q100. The ultimate goal of software testing is:
(A) Deliver reliable, defect-free, and user-acceptable software
(B) Hardware setup only
(C) UI design only
(D) Database only
Answer: (A) Deliver reliable, defect-free, and user-acceptable software

Exit mobile version