1.​ What is the primary purpose of boundary value analysis?

​
Options:

●​ To test the input at its minimum and maximum limits

●​ To analyze system performance at boundaries
●​ To verify the integration between modules
●​ To automate test scripts
●​ None of the above

2.​ Which of the following is NOT a valid activity during test closure?​
Options:

●​ Documenting test results

●​ Archiving testware
●​ Writing test cases
●​ Conducting lessons learned meetings
●​ Updating test summary report

3.​ What kind of testing verifies that changes have not adversely affected existing
functionalities?​
Options:

●​ Unit Testing
●​ Regression Testing
●​ Smoke Testing
●​ Sanity Testing
●​ Acceptance Testing

4.​ What does the term "test oracle" refer to?​

Options:

●​ Tool used for test automation

●​ Source to determine expected results for a test
●​ The person performing the test
●​ Test environment setup
●​ Test case documentation

5.​ Which technique is commonly used for prioritizing test cases?​

Options:

●​ Risk-Based Testing
●​ Exploratory Testing
●​ Boundary Value Testing
●​ Equivalence Partitioning
●​ State Transition Testing
6.​ What does a “test harness” consist of in automated testing?​
Options:

●​ Test data only

●​ Environment setup only
●​ Drivers and stubs for testing
●​ Test plan and strategy
●​ Test completion criteria

7.​ What is cyclomatic complexity used to measure?​

Options:

●​ Number of defects in the code

●​ Number of paths in a program's control flow graph
●​ Test coverage percentage
●​ Defect density
●​ Requirement volatility

8.​ Which document defines the details of test conditions, inputs, and expected results?​
Options:

●​ Test Strategy
●​ Test Plan
●​ Test Case Specification
●​ Incident Report
●​ Traceability Matrix

9.​ In Agile methodologies, what is the role of the tester in a sprint?​

Options:

●​ Write test cases only

●​ Automate all tests
●​ Collaborate continuously and perform exploratory testing
●​ Report bugs at the end of the sprint
●​ Validate only acceptance criteria

10.​Which of the following is NOT a part of the defect life cycle?​

Options:

●​ Identification
●​ Logging
●​ Fixing
●​ Verification
●​ Deletion of test cases
11.​What is a “Test Stub”?​
Options:

●​ A simulated module called by a module under test

●​ A driver module that calls lower modules
●​ A defect logging tool
●​ A tool for performance testing
●​ A form of test documentation

12.​What is the main goal of load testing?​

Options:

●​ To verify application functionality under normal conditions

●​ To check system behavior under peak user load
●​ To detect usability issues
●​ To find security vulnerabilities
●​ To perform code coverage analysis

13.​Which of the following is true about smoke testing?​

Options:

●​ It is done after completion of functional testing

●​ It checks basic functionality and determines if further testing can proceed
●​ It is another term for regression testing
●​ It is done by developers only
●​ It is performed at the end of the project

14.​What is “equivalence partitioning”?​

Options:

●​ Dividing test cases based on business modules

●​ Partitioning input data into valid and invalid classes
●​ Dividing test effort among team members
●​ Partitioning requirements for usability testing
●​ Segregating functional and non-functional testing

15.​What does “code coverage” measure?​

Options:

●​ Number of tests executed

●​ Percentage of code executed by tests
●​ Number of defects found
●​ Test execution time
●​ Defect severity
16.​What kind of testing is performed without any knowledge of the internal workings of the
application?​
Options:

●​ White-box Testing
●​ Black-box Testing
●​ Grey-box Testing
●​ Code Coverage Testing
●​ Unit Testing

17.​Which of the following is NOT an output of the test planning phase?​

Options:

●​ Test schedule
●​ Test environment setup
●​ Risk assessment
●​ Defect management process
●​ Test completion report

18.​What is meant by “test data”?​

Options:

●​ Data created to verify correct behavior of the application

●​ The environment where tests are run
●​ Test cases and test scripts
●​ Test execution reports
●​ Cost and resource estimates for testing

19.​Which tool is best suited for static code analysis?​

Options:

●​ JIRA
●​ Selenium
●​ SonarQube
●​ Postman
●​ JMeter

20.​What kind of testing focuses on user experience and interface designs?​

Options:

●​ Usability Testing
●​ Load Testing
●​ Integration Testing
●​ Unit Testing
●​ Regression Testing
21.​What is the defect density formula?​
Options:

●​ Defects found / Total tests executed

●​ Defects found / Size of software module
●​ Defects found / Total time taken for testing
●​ Defects found / Total users
●​ Defects found / Number of test cases

22.​What is the primary activity in a test execution phase?​

Options:

●​ Test case design

●​ Test environment setup
●​ Running test cases and logging results
●​ Reviewing requirements
●​ Planning future tests

23.​Which is a drawback of automated testing?​

Options:

●​ Human errors in writing scripts

●​ Expensive initial cost and maintenance
●​ Inability to repeat tests
●​ Cannot perform regression testing
●​ None of the above

24.​In which type of testing is “test coverage” most applicable?​

Options:

●​ Unit testing
●​ Integration testing
●​ Functional testing
●​ Acceptance testing
●​ Usability testing

25.​Which of the following is NOT a valid way to prioritize defects?​

Options:

●​ Severity
●​ Frequency of occurrence
●​ Cost to fix
●​ Developer preference
●​ Impact on user
26.​What is the meaning of “traceability matrix”?​
Options:

●​ A document matching test cases to requirements

●​ A tool to log defects
●​ Documentation of test environment details
●​ A list of test scripts automated
●​ Performance test results

27.​What is the typical input for risk-based testing?​

Options:

●​ Requirement priorities and business impact

●​ Historical defect data only
●​ Test environment details
●​ Test execution schedule
●​ Project budget

28.​What does “entry criteria” define in testing?​

Options:

●​ The conditions to start testing activities

●​ The plan for writing test cases
●​ The process for defect fixing
●​ The testing completion conditions
●​ Criteria for production deployment

29.​What kind of tests are “negative tests”?​

Options:

●​ Tests that check system behavior with invalid inputs

●​ Tests that check code performance
●​ Tests that check integration points
●​ Tests that verify accessibility
●​ Tests performed only after system testing

30.​Which of the following is NOT part of Non-Functional Testing?​

Options:

●​ Performance Testing
●​ Security Testing
●​ Usability Testing
●​ Functional Testing
●​ Load Testing
31.​Which testing validates the system’s compliance with business requirements?​
Options:

●​ System Testing
●​ Acceptance Testing
●​ Unit Testing
●​ Integration Testing
●​ Regression Testing

32.​What is a "test case priority" primarily based on?​

Options:

●​ Developer skill level

●​ Business impact and risk
●​ Test case length
●​ Number of lines of code tested
●​ Tester availability

33.​Which of the following is NOT a characteristic of good test cases?​

Options:

●​ Reproducible
●​ Clear and concise
●​ Independent of each other
●​ Ambiguous test steps
●​ Traceable to requirements

34.​What is "test automation framework" designed for?​

Options:

●​ Defining code standards

●​ Providing guidelines for automated tests
●​ Writing test cases manually
●​ Creating build scripts
●​ Monitoring live systems

35.​What kind of bug is caused by concurrency issues in multi-threaded applications?​

Options:

●​ Syntax bug
●​ Deadlock
●​ Security vulnerability
●​ Usability defect
●​ Data mismatch
36.​What is "exploratory testing"?​
Options:

●​ Testing without pre-written test cases

●​ Automated testing of all functional requirements
●​ Code inspection before testing
●​ Regression testing after release
●​ Load testing for performance

37.​Which of the following is considered a static testing technique?​

Options:

●​ Code Review
●​ Unit Testing
●​ System Testing
●​ Performance Testing
●​ Security Testing

38.​What is the primary benefit of continuous integration in testing?​

Options:

●​ Automated creation of test cases

●​ Faster feedback on code changes
●​ Eliminates the need for manual testing
●​ Reduces the number of testers required
●​ Converts manual tests to automated tests

39.​Which type of testing checks the software’s behavior under stress or high loads?​
Options:

●​ Stress Testing
●​ Functional Testing
●​ Usability Testing
●​ Regression Testing
●​ Sanity Testing

40.​What does "negative testing" help to validate?​

Options:

●​ System performance under peak load

●​ System response to invalid or unexpected input
●​ System’s UI consistency
●​ Integration between modules
●​ System’s compliance with security policies
41.​Which of the following best describes “test script”?​
Options:

●​ A manual test case documentation

●​ Automated test instructions to be executed by tools
●​ A code review checklist
●​ A project management document
●​ None of the above

42.​What is the purpose of "defect triage" meetings?​

Options:

●​ Prioritize and assign defects for fixing

●​ Write new test cases for defects
●​ Schedule test execution
●​ Review test automation progress
●​ Prepare documentation for release

43.​Which of the following defines exit criteria for testing?​

Options:

●​ Maximum number of defects allowed before stopping

●​ Completion status of all planned test cases and fixes
●​ Availability of testing team
●​ Project manager’s decision
●​ Initial project requirements

44.​What does "test coverage" refer to?​

Options:

●​ Percentage of requirements tested

●​ Number of testers involved
●​ Percentage of defects found
●​ Number of test cases written
●​ Time spent on testing

45.​What is the function of a test driver in bottom-up integration testing?​

Options:

●​ Simulate higher-level module

●​ Simulate lower-level module
●​ Manage test data
●​ Record defects
●​ Execute test cases
46.​Which of these is NOT an advantage of automated testing?​
Options:

●​ Increases test coverage

●​ Provides faster feedback
●​ Eliminates the need for human judgement
●​ Reduces repetitive manual effort
●​ Works well for regression testing

47.​What technique is useful for identifying hidden relationships between input variables in
testing?​
Options:

●​ Decision Table Testing

●​ Boundary Value Analysis
●​ Exploratory Testing
●​ Smoke Testing
●​ Sanity Testing

48.​What does "functional baseline" mean in software testing?​

Options:

●​ The original version of code approved for testing

●​ The first set of test cases written
●​ The final testing report
●​ The database setup for tests
●​ The defect log

49.​Which of the following is NOT typically part of configuration management in testing?​

Options:

●​ Version control
●​ Defect tracking
●​ Test data management
●​ Test case automation
●​ Build management

50.​What does "alpha testing" mean?​

Options:

●​ Testing performed by end-users outside the development site

●​ Testing performed by users inside the development organization
●​ Automated testing framework setup
●​ System integration testing
●​ Final product release testing
51.​Which type of testing is best suited for verifying user permissions and access control?​
Options:

●​ Security Testing
●​ Usability Testing
●​ Regression Testing
●​ Load Testing
●​ Functional Testing

52.​What is the main purpose of traceability in requirements management?​

Options:

●​ To ensure each requirement is covered by test cases

●​ To document defects encountered
●​ To automate test execution
●​ To measure test execution time
●​ To prioritize test cases

53.​What is “boundary testing” primarily concerned with?​

Options:

●​ Testing values at the edges of input domains

●​ Testing functionality across system modules
●​ Testing database transactions
●​ Testing APIs under load
●​ Testing user interface responsiveness

54.​What does “test execution” involve?​

Options:

●​ Running test cases and recording results

●​ Writing test cases
●​ Defining test objectives
●​ Setting up the test environment
●​ Generating test data

55.​Which of the following is NOT a typical test level?​

Options:

●​ Unit Testing
●​ Integration Testing
●​ System Testing
●​ Compliance Testing
●​ Acceptance Testing
56.​What is the purpose of “test estimation”?​
Options:

●​ To predict the effort and time required for testing activities

●​ To find defects
●​ To prioritize test cases
●​ To prepare test scripts
●​ To automate test execution

57.​In software testing, what does “drain testing” verify?​

Options:

●​ Ability to handle gradual reduction of system resources

●​ Software’s response to unexpected inputs
●​ Integration between modules
●​ Security vulnerabilities
●​ Performance under peak traffic

58.​What is NOT a typical characteristic of “good” test data?​

Options:

●​ Representative of real scenarios

●​ Covers boundary conditions
●​ Contains only valid data
●​ Includes invalid and unexpected data
●​ Maintains privacy and confidentiality

59.​Which type of test document usually contains detailed steps and expected results?​
Options:

●​ Test Case Specification

●​ Test Plan
●​ Test Summary Report
●​ Defect Report
●​ Test Strategy

60.​What is “smoke testing” mainly designed for?​

Options:

●​ To verify build stability before detailed testing

●​ To test the entire system
●​ To test the database
●​ To test a specific module
●​ To evaluate user experience
61.​Which testing activity is mainly focused on finding gaps in the system's business flow?​
Options:

●​ Business Process Testing

●​ Security Testing
●​ Usability Testing
●​ Load Testing
●​ Code Coverage Testing

62.​Which type of testing is performed to ensure that software conforms to specified

standards?​
Options:

●​ Compliance Testing
●​ Performance Testing
●​ Regression Testing
●​ Usability Testing
●​ Functional Testing

63.​What is “test oracle” in software testing?​

Options:

●​ A mechanism to determine expected outcomes and verify actual results

●​ A tool for automating tests
●​ A defect tracking system
●​ The environment setup for testing
●​ The test team's lead person

64.​Which phase defines the exit criteria for formal testing closure?​
Options:

●​ Test Closure
●​ Test Execution
●​ Test Planning
●​ Test Design
●​ Test Development

65.​What does “pair testing” mean?​

Options:

●​ Two testers working together on the same test

●​ Automated tests running in pairs
●​ Testing two modules at the same time
●​ Regression testing performed in pairs
●​ Testing two defects simultaneously
66.​Which of the following best describes “test harness”?​
Options:

●​ Set of software tools and test drivers to execute tests

●​ Documentation of test cases
●​ Schedule of test activities
●​ Defect tracking application
●​ Code review tool

67.​What is “condition coverage” in white box testing?​

Options:

●​ Coverage of all possible decision outcomes

●​ Coverage of all functional requirements
●​ Testing all boundary values
●​ Measuring percentage of executed test cases
●​ Checking all security vulnerabilities

68.​What is a “latent defect”?​

Options:

●​ A defect that exists but has not yet been detected by testing
●​ A defect detected during testing
●​ A defect found in production after release
●​ A defect fixed before release
●​ A trivial usability defect

69.​What is the purpose of a “test summary report”?​

Options:

●​ To provide stakeholders with testing outcomes and recommendations

●​ To list test cases executed
●​ To document defects found
●​ To describe testing tools used
●​ To track test schedule progress

70.​What is “configuration management” in software testing?​

Options:

●​ Controlling and tracking changes in software and test artifacts

●​ Managing the test team
●​ Automating test scripts
●​ Running performance tests
●​ Writing test cases
71.​What type of testing is done to verify the accessibility of software?​
Options:

●​ Accessibility Testing
●​ Functional Testing
●​ Security Testing
●​ Performance Testing
●​ Regression Testing

72.​What is the main objective of regression testing?​

Options:

●​ To ensure fixes have not introduced new defects

●​ To check performance bottlenecks
●​ To verify user interface design
●​ To validate security requirements
●​ To perform integration testing

73.​Which of these documents outlines the testing approach and scope?​

Options:

●​ Test Plan
●​ Test Case Specification
●​ Defect Report
●​ Test Environment Setup
●​ Traceability Matrix

74.​What is the primary difference between verification and validation?​

Options:

●​ Verification checks if the product is built correctly; validation checks if the right product
is built
●​ Verification is manual; validation is automated
●​ Verification is done before coding; validation after release
●​ Verification tests functionality; validation tests security
●​ There is no difference

75.​What is the meaning of "test coverage gap"?​

Options:

●​ Areas of the application not covered by tests

●​ Defects not found by testing
●​ Test cases not executing fully
●​ Test environment issues
●​ Testers’ unavailability
76.​What is “cyclomatic complexity” used for in testing?​
Options:

●​ Estimating the complexity of a program’s control flow

●​ Measuring defect density
●​ Calculating test execution time
●​ Tracking test case effectiveness
●​ Automating test scripts

77.​Which of the following is NOT part of a defect report?​

Options:

●​ Defect description
●​ Steps to reproduce
●​ Root cause analysis
●​ Tester's personal opinion
●​ Severity and priority

78.​Which testing type focuses on checking the software usability?​

Options:

●​ Usability Testing
●​ Load Testing
●​ Security Testing
●​ Integration Testing
●​ Unit Testing

79.​On which document would you typically find the “entry criteria” and “exit criteria” for
testing?​
Options:

●​ Test Plan
●​ Test Case Document
●​ Defect Report
●​ Test Summary Report
●​ Traceability Matrix

80.​What does a “test stub” do in integration testing?​

Options:

●​ Simulates a called module that is not yet integrated

●​ Automates regression tests
●​ Collects defect statistics
●​ Simulates the user interface
●​ Creates test data
81.​Which is NOT a commonly used defect severity level?​
Options:

●​ Critical
●​ High
●​ Medium
●​ Low
●​ Trivial
●​ Optional

82.​What is the main goal of usability testing?​

Options:

●​ Assess the ease of use and user satisfaction

●​ Validate functional requirements
●​ Measure performance under load
●​ Test security vulnerabilities
●​ Check code quality

83.​What is meant by “static testing”?​

Options:

●​ Testing without executing code

●​ Testing with automated tools only
●​ Executing test cases manually
●​ Testing done only in production
●​ Testing non-functional requirements

84.​When is "alpha testing" typically performed?​

Options:

●​ Before releasing software to external users

●​ After release
●​ During system testing
●​ After regression testing
●​ During unit testing

85.​What is the main output from a test design phase?​

Options:

●​ Test cases and test scripts

●​ Test environment setup
●​ Defect Logs
●​ Project Status Report
●​ Test summary report
86.​What is “test data validity” used for?​
Options:

●​ Ensuring the test data is relevant and accurate for test cases
●​ Automating test scripts
●​ Generating random inputs
●​ Measuring the number of test cases executed
●​ Defect tracking

87.​Which type of testing is intended to verify software scalability?​

Options:

●​ Load Testing
●​ Functional Testing
●​ Security Testing
●​ Usability Testing
●​ Unit Testing

88.​What is “defect cascading”?​

Options:

●​ One defect causing multiple related defects in the software

●​ Multiple defects found during a single test case
●​ Defects fixed together in one release
●​ Defects reported by different users
●​ Defects ignored due to low priority

89.​What is the advantage of “test-driven development” (TDD)?​

Options:

●​ Tests are written before the code, improving design and quality
●​ Testing is done at the end of the project
●​ Manual testing is eliminated completely
●​ Defects are automatically fixed
●​ Test cases are reused without modification

90.​What is the role of “traceability matrix” in testing?​

Options:

●​ Mapping test cases to requirements to ensure coverage

●​ Scheduling test execution
●​ Automating defect reporting
●​ Managing the test environment
●​ Tracking tester productivity
91.​What is the typical cause of “flaky tests” in automation?​
Options:

●​ Tests that intermittently pass or fail due to environment or timing issues

●​ Defects in the application code
●​ Missing test data
●​ Incorrect test steps
●​ Outdated test scripts

92.​Which technique involves examining a software system without executing it?​

Options:

●​ Static testing
●​ Dynamic testing
●​ Regression testing
●​ Exploratory testing
●​ Load testing

93.​Which of the following describes “test closure” activities?​

Options:

●​ Gathering test artifacts, lessons learned, and final reporting

●​ Writing test cases
●​ Executing test cases
●​ Fixing defects
●​ Automating tests

94.​What does “defect severity” define?​

Options:

●​ Impact of a defect on the system or users

●​ Number of defects found
●​ Priority of fixing defects
●​ Time taken to fix the defect
●​ Tester who found the defect

95.​Which is NOT a goal of performance testing?​

Options:

●​ Measuring response times

●​ Identifying bottlenecks
●​ Verifying functional correctness
●​ Evaluating scalability
●​ Determining throughput
96.​What is the significance of “test environment”?​
Options:

●​ It is the setup where testing is conducted, including hardware, software, and network
●​ The schedule for testing activities
●​ Documentation of test cases
●​ Defect logging tool
●​ Automated testing framework

97.​Which of the following is NOT a common software testing principle?​

Options:

●​ Testing shows the presence of defects

●​ Exhaustive testing is possible
●​ Early testing saves time and cost
●​ Defects cluster in certain modules
●​ Testing is context-dependent

98.​What kind of testing is done to check software behavior during power failures or system
crashes?​
Options:

●​ Recovery Testing
●​ Security Testing
●​ Load Testing
●​ Usability Testing
●​ Integration Testing

99.​Which of the following correctly defines “test coverage”?​

Options:

●​ Measure of how much source code or requirements are exercised by tests

●​ Amount of time spent testing
●​ Number of defects detected
●​ Number of test cases automated
●​ Number of testers in the team

100.​ What is the primary advantage of risk-based testing?​

Options:

●​ Focuses test efforts on areas of highest risk to improve test efficiency

●​ Testing all modules equally
●​ Runs tests only after development is complete
●​ Eliminates manual testing completely
●​ Automates all tests at once
101.​ What is the role of "test data management" in software testing?​
Options:

●​ Creating, maintaining, and protecting test data sets for various testing needs
●​ Writing test cases
●​ Automating test scripts
●​ Logging defects
●​ Scheduling test execution

102.​ Which of the following describes "isolation testing"?​

Options:

●​ Testing components individually with stubs or drivers simulating others

●​ Testing integrated system functionality
●​ Automated regression testing
●​ Load testing
●​ Usability testing

103.​ What is the function of a "test coverage tool"?​

Options:

●​ Measure which parts of code or requirements have been tested

●​ Log defects
●​ Automate performance tests
●​ Generate test data
●​ Schedule test cases

104.​ What is "code instrumentation" in testing?​

Options:

●​ Inserting additional code to measure coverage or execution details

●​ Writing automation scripts
●​ Logging defects
●​ Running manual tests
●​ Setting up test environment

105.​ Define "maintenance testing".​

Options:

●​ Testing of changes made to software after release or during software maintenance phase
●​ Initial system testing
●​ Regression testing during development
●​ Performance testing
●​ Security testing
106.​ What is the purpose of "test point analysis"?​
Options:

●​ Estimate testing effort based on software size and complexity

●​ Log defects
●​ Write test cases
●​ Manage test environments
●​ Automate test scripts

107.​ What is "smoke testing"?​

Options:

●​ Preliminary test to check major functionalities for stability after a new build
●​ Detailed functional testing
●​ Load testing
●​ Security testing
●​ Usability testing

108.​ What is "test case prioritization"?​

Options:

●​ Ordering test cases to be executed based on criticality and risk

●​ Writing test cases first
●​ Scheduling team shifts
●​ Defect priority setting
●​ Automating test scripts

109.​ What is the purpose of "configuration management" in testing?​

Options:

●​ Control and manage changes to test artifacts and environment

●​ Write test cases
●​ Test automation development
●​ User acceptance testing
●​ Security audits

110.​ What is "defect severity"?​

Options:

●​ Degree of impact a defect has on the system's operation

●​ Time taken to fix the defect
●​ Number of defects found by tester
●​ Defect detection technique
●​ Priority to fix a defect
111.​ Which testing technique uses decision tables?​
Options:

●​ Business rule testing

●​ Performance testing
●​ Load testing
●​ Regression testing
●​ Security testing

112.​ What is "test automation script maintenance"?​

Options:

●​ Updating automated scripts to align with application changes

●​ Writing new manual test cases
●​ Logging defects
●​ Writing test plans
●​ Scheduling regression tests

113.​ What does “test drift” refer to in automation testing?​

Options:

●​ When automated tests become outdated due to application changes

●​ Test cases that run in parallel
●​ Defect leaking from automation
●​ Test environment failures
●​ Tester errors

114.​ What is the meaning of "defect aging"?​

Options:

●​ Time elapsed between defect detection and resolution

●​ Number of defects found
●​ Severity of defects
●​ Defect priority
●​ Test case execution time

115.​ What is the primary goal of accessibility testing?​

Options:

●​ Ensure software is usable by people with disabilities

●​ Test software speed
●​ Check data security
●​ Validate functional requirements
●​ Execute regression suites
116.​ Which of the following is NOT part of the testing process?​
Options:

●​ Requirement gathering
●​ Test planning
●​ Defect fixing
●​ Test execution
●​ Test reporting

117.​ What is the role of "test lead" in the QA process?​

Options:

●​ Planning, coordinating, and leading testing activities

●​ Writing code
●​ Designing UI
●​ Managing customer support
●​ Creating user manuals

118.​ Which is NOT a type of testing?​

Options:

●​ Unit testing
●​ Integration testing
●​ System testing
●​ Project management testing
●​ Acceptance testing

119.​ What is "defect triage"?​

Options:

●​ Reviewing and prioritizing defects before fixing

●​ Writing test cases
●​ Automating scripts
●​ Executing test plans
●​ Scheduling builds

120.​ What is the purpose of "performance testing"?​

Options:

●​ Assess software responsiveness, stability, and scalability under load

●​ Testing UI layout
●​ Executing unit tests
●​ Logging defects
●​ Automating test cases
121.​ What is "boundary value analysis"?​
Options:

●​ Technique to test input values at boundaries

●​ Testing error handling
●​ Testing UI responsiveness
●​ Security auditing
●​ Performance benchmarking

122.​ What is the difference between alpha and beta testing?​

Options:

●​ Alpha is internal testing; beta is external by users

●​ Beta is performed inside dev team; alpha is external
●​ Alpha is automated; beta is manual
●​ Alpha is for performance; beta for security
●​ No difference

123.​ Which testing type focuses on checking software interoperability?​

Options:

●​ Compatibility Testing
●​ Load testing
●​ Usability testing
●​ Security testing
●​ Functional testing

124.​ What does “test plan” include?​

Options:

●​ Scope, approach, schedule, resources, and deliverables of testing

●​ List of defects
●​ Automation scripts
●​ Test environment configs
●​ User manuals

125.​ What is "static testing"?​

Options:

●​ Reviewing documents or code without execution

●​ Executing test scripts
●​ Running automated scripts
●​ Performance monitoring
●​ Security audits
126.​ Which is a characteristic of "good test case"?​
Options:

●​ Clear and concise

●​ Ambiguous
●​ Incomplete
●​ Complex to understand
●​ Untraceable

127.​ What does "defect leakage" measure?​

Options:

●​ Defects found in production after testing

●​ Defects fixed late
●​ Defects ignored
●​ Duplicate defects
●​ Defects reported by users

128.​ What is the purpose of "test environment"?​

Options:

●​ Hardware and software setup for testing

●​ Defect log
●​ Test case repository
●​ Automation scripts folder
●​ Test plan document

129.​ Which of the following is NOT a test type?​

Options:

●​ Regression testing
●​ Smoke testing
●​ Debugging
●​ Load testing
●​ User acceptance testing

130.​ What is "root cause analysis" in defect management?​

Options:

●​ Identifying underlying cause of defects

●​ Logging defects
●​ Prioritizing defects
●​ Automating tests
●​ Scheduling releases
131.​ What is “exploratory testing”?​
Options:

●​ Simultaneous learning, design, and execution without scripts

●​ Automated regression testing
●​ Load testing
●​ Security testing
●​ Static testing

132.​ What is the goal of "test case design"?​

Options:

●​ Create detailed steps to validate software requirements

●​ Execute test scripts
●​ Log defects
●​ Automate tests
●​ Monitor performance

133.​ What is the role of "test metrics"?​

Options:

●​ Measure and track testing progress and quality

●​ Write test cases
●​ Log defects
●​ Automate tests
●​ Schedule testing

134.​ Which tool is commonly used for bug tracking?​

Options:

●​ JIRA
●​ Selenium
●​ JMeter
●​ Jenkins
●​ Postman

135.​ What is "test script"?​

Options:

●​ Automated or manual instructions to perform a test

●​ Defect log
●​ Test plan document
●​ Requirement specification
●​ Test summary report
136.​ What is "defect severity"?​
Options:

●​ Impact level of defect on system functionality

●​ Tester’s experience level
●​ Test case count
●​ Automation status
●​ Test schedule

137.​ What is “risk-based testing”?​

Options:

●​ Prioritize testing on high-risk areas to optimize effort

●​ Test all features equally
●​ Automate all tests
●​ Test only security features
●​ Skip low-priority defects

138.​ What is "test closure"?​

Options:

●​ Finalizing testing activities and deliverables

●​ Starting test execution
●​ Writing test cases
●​ Defect fixing
●​ Automating tests

139.​ What is “unit testing”?​

Options:

●​ Testing smallest software components or functions

●​ End-to-end system testing
●​ Integration testing
●​ Acceptance testing
●​ Usability testing

140.​ What is “test coverage”?​

Options:

●​ Measure of the extent of testing done against requirements or code

●​ Number of testers deployed
●​ Defect counts
●​ Test execution time
●​ Automation script count
141.​ What is "risk-based testing"?​
Options:

●​ Testing guided by risks to prioritize test cases and resources

●​ Testing all features equally
●​ Automated regression testing
●​ Usability testing only
●​ Performance testing

142.​ What is "fuzz testing"?​

Options:

●​ Testing with random or invalid data to find vulnerabilities

●​ Load testing
●​ Security testing
●​ Usability testing
●​ Integration testing

143.​ Which testing technique uses decision tables?​

Options:

●​ Decision Table Testing

●​ Boundary Value Analysis
●​ Exploratory Testing
●​ Smoke Testing
●​ Sanity Testing

144.​ What is the purpose of "cause-effect graphing"?​

Options:

●​ To represent the relationship between inputs (causes) and outputs (effects) for test design
●​ Automate test cases
●​ Record defects
●​ Run regression tests
●​ Plan test execution

145.​ What is "pairwise testing"?​

Options:

●​ Testing all possible pairs of input parameters to reduce test cases

●​ Testing two test cases together
●​ Running tests in parallel by two testers
●​ Testing two modules simultaneously
●​ Load testing in pairs
146.​ What is "state transition testing"?​
Options:

●​ Testing based on state machine diagrams to verify state changes

●​ Testing database triggers
●​ Api testing
●​ Automation scripting
●​ User acceptance testing

147.​ What is "use case testing"?​

Options:

●​ Testing real-world scenarios reflecting user interactions

●​ Testing internal code structure
●​ Performance testing
●​ Integration testing
●​ Load testing

148.​ Define "equivalence class partitioning".​

Options:

●​ Dividing input data into valid and invalid classes to reduce test cases
●​ Segmenting the team for testing
●​ Classifying defects by severity
●​ Scheduling test execution
●​ Automation scripting

149.​ What is "boundary value analysis"?​

Options:

●​ Testing at the edges of input domains where errors often occur

●​ Random testing
●​ Load testing
●​ Security testing
●​ Exploratory testing

150.​ What is "error guessing" in testing?​

Options:

●​ Using experience to identify error-prone areas to create test cases

●​ Automated error detection
●​ Writing detailed test scripts
●​ Regression testing
●​ Performance monitoring
151.​ What is "all-pairs testing"?​
Options:

●​ Testing all combinations of pairs of input parameters to optimize coverage

●​ Testing two automation scripts
●​ Pair programming
●​ Load testing
●​ Security scanning

152.​ What is "risk coverage testing"?​

Options:

●​ Testing focused on areas assessed as high-risk for failure

●​ Testing all functionality equally
●​ Performance testing only
●​ Usability testing only
●​ Security testing only

153.​ What is "statement coverage" in white box testing?​

Options:

●​ Percentage of code statements executed by tests

●​ Number of defects found
●​ Test duration
●​ Number of test cases executed
●​ Automation coverage

154.​ What is "branch coverage"?​

Options:

●​ Coverage of all decision points such as if-else conditions

●​ UI testing coverage
●​ Performance benchmarks
●​ Security audit coverage
●​ Regression coverage

155.​ What is "test analysis"?​

Options:

●​ Reviewing test basis and identifying test conditions and risks

●​ Executing test scripts
●​ Automating test cases
●​ Logging defects
●​ Preparing test environment
156.​ How does "continuous integration" enhance testing?​
Options:

●​ Provides automated build and test feedback on code changes frequently

●​ Eliminates all manual testing
●​ Increases number of test cases
●​ Reduces developers’ workload
●​ Manages defects

157.​ What is "exploratory testing"?​

Options:

●​ Testing without predefined test cases and relying on tester’s knowledge

●​ Automated functional testing
●​ Regression testing
●​ Security testing
●​ Performance testing

158.​ What is "test efficiency"?​

Options:

●​ Ratio of defects detected to effort spent in testing

●​ Number of test cases executed
●​ Number of automation scripts
●​ Test environment setup time
●​ Test data volume

159.​ What is the objective of "test environment management"?​

Options:

●​ Maintain availability and stability of test environments for consistent testing

●​ Writing test cases
●​ Logging defects
●​ Executing test scripts
●​ Automating tests

160.​ What is the difference between "load testing" and "stress testing"?​
Options:

●​ Load testing evaluates behavior under expected load; stress testing tests beyond capacity
to failure
●​ Load testing is manual; stress testing automated
●​ Load testing is functional; stress testing security
●​ Load testing is done post-release; stress testing pre-release
●​ No difference
161.​ What is "test script review"?​
Options:

●​ Evaluating automated test scripts for correctness and maintainability

●​ Writing manual test cases
●​ Logging defects
●​ Automating test execution
●​ Test planning

162.​ What is meant by "test case design techniques"?​

Options:

●​ Methods to create effective and optimized test cases

●​ Writing test scripts
●​ Automation only
●​ Defect tracking
●​ Performance monitoring

163.​ What is "testware"?​

Options:

●​ All artifacts produced during testing including test cases, scripts, and data
●​ Code only
●​ Defects only
●​ Test results only
●​ User manuals

164.​ Which of these is NOT a non-functional testing type?​

Options:

●​ Functional Testing
●​ Load Testing
●​ Security Testing
●​ Usability Testing
●​ Performance Testing

165.​ Which of the following is a negative testing example?​

Options:

●​ Entering invalid inputs and observing the behavior

●​ Valid input testing
●​ API response validation
●​ UI functionality testing
●​ Regression testing
166.​ What is "API testing"?​
Options:

●​ Testing application programming interfaces for expected functionality and reliability

●​ GUI testing
●​ Performance testing
●​ Security testing
●​ Unit testing

167.​ What is "test data masking"?​

Options:

●​ Masking sensitive data in test environments to ensure data privacy

●​ Creating test cases
●​ Automation scripting
●​ Logging defects
●​ Scheduling tests

168.​ What is "test automation framework"?​

Options:

●​ A structure providing guidelines and reusable components for automation

●​ Defect report database
●​ Test execution schedule
●​ Requirement documentation
●​ User acceptance plan

169.​ What is "test defect"?​

Options:

●​ Variance from expected behavior observed during testing

●​ Test case
●​ Automation script
●​ Test plan
●​ Execution log

170.​ What is the purpose of "test schedule"?​

Options:

●​ Defining timelines for test activities

●​ Logging defects
●​ Writing test cases
●​ Automating scripts
●​ Monitoring test environment
171.​ What is "test coverage analysis"?​
Options:

●​ Measuring how much of the system or code is tested

●​ Defect fixing process
●​ Automation framework setup
●​ Test planning
●​ Performance monitoring

172.​ What is "smoke testing"?​

Options:

●​ Initial testing to check basic system functionality after a new build

●​ Full regression testing
●​ Load testing
●​ Usability testing
●​ Security scanning

173.​ What is the key purpose of “verification” in software testing?​

Options:

●​ Ensuring the product is built correctly according to specifications

●​ Ensuring the product meets user needs
●​ Finding security vulnerabilities
●​ Improving performance
●​ Fixing defects

174.​ What is “validation” in software testing?​

Options:

●​ Ensuring the product meets the user’s actual requirements and expectations
●​ Checking code syntax
●​ Automating test scripts
●​ Logging defects
●​ Performance tuning

175.​ What is a "test plan"?​

Options:

●​ Document detailing scope, approach, resources, and schedule for testing

●​ Defect log
●​ Test report
●​ Automation scripts
●​ Requirement document
176.​ Which software testing methodology involves iterative development and continuous
feedback?​
Options:

●​ Agile
●​ Waterfall
●​ V-Model
●​ Spiral
●​ Big Bang

177.​ What is the key characteristic of the Waterfall testing model?​

Options:

●​ Sequential phases with verification after implementation

●​ Iterative and incremental testing
●​ Test-driven development
●​ Continuous integration testing
●​ Automated regression testing

178.​ What is "state transition testing"?​

Options:

●​ Testing based on state changes in the software with defined inputs and outputs
●​ Load testing
●​ Security testing
●​ Usability testing
●​ Automation testing

179.​ In "cause-effect graphing," what do causes and effects represent?​

Options:

●​ Input conditions and corresponding outputs or actions

●​ Defect sources and impacts
●​ Testers and developers
●​ Automation scripts and results
●​ Requirements and designs

180.​ What is the benefit of using decision table testing?​

Options:

●​ Systematically cover combinations of inputs with corresponding outputs

●​ Test only valid inputs
●​ Automate regression tests
●​ Test performance benchmarks
●​ Track defects efficiently
181.​ Which of the following best matches "error guessing" testing?​
Options:

●​ Relying on tester intuition and experience to guess error-prone areas

●​ Automated boundary testing
●​ Performance testing with random inputs
●​ Systematic regression testing
●​ Security vulnerability scanning

182.​ What is the "all-pairs" or "pairwise" testing approach?​

Options:

●​ Testing all possible pairs of input values to optimize coverage

●​ Testing two modules at once
●​ Running two automation scripts simultaneously
●​ Conducting load tests in pairs
●​ Pair programming technique

183.​ When is it most appropriate to use equivalence partitioning?​

Options:

●​ To reduce the number of test cases by grouping similar inputs

●​ For testing security vulnerabilities
●​ For performance benchmarking
●​ During code reviews
●​ For usability testing

184.​ What is the role of a "test driver" during integration testing?​

Options:

●​ Simulate higher-level modules that are not yet integrated

●​ Automate test case execution
●​ Log defects found during testing
●​ Generate test metrics
●​ Manage the test environment

185.​ What is the purpose of a "test baseline"?​

Options:

●​ A formally reviewed version of software or documents used as reference for testing

●​ Current defect listing
●​ Test case repository
●​ Automation script library
●​ Test environment configuration
186.​ What distinguishes "regression testing" from other testing types?​
Options:

●​ Ensuring that code changes do not adversely affect existing functionality

●​ Testing initial requirements only
●​ Performing exploratory testing
●​ Focused on UI only
●​ Done by end users

187.​ What is the best description of "test coverage"?​

Options:

●​ The extent to which test cases exercise the software's code or requirements
●​ Number of testers employed
●​ Number of bugs found
●​ Time consumed in testing
●​ Amount of automated tests

188.​ What is "flaky test"?​

Options:

●​ A test that sometimes passes and sometimes fails without code changes
●​ Test case with no defects
●​ Automated test script that never runs
●​ Test case written for invalid data
●​ Performance test

189.​ What is "test data masking"?​

Options:

●​ Protecting sensitive data by obscuring it in test environments

●​ Writing test data manually
●​ Automating data generation
●​ Creating synthetic data
●​ Test log file

190.​ What is the benefit of integrating automated testing in CI/CD pipelines?​

Options:

●​ Provide quick feedback on code changes and reduce manual testing effort
●​ Replace manual testing completely
●​ Automatically fix bugs
●​ Document requirements
●​ Schedule release dates
191.​ What is "test analysis"?​
Options:

●​ Reviewing requirements and identifying test conditions

●​ Executing test cases
●​ Automating tests
●​ Defect reporting
●​ Environment setup

192.​ Which is NOT a benefit of exploratory testing?​

Options:

●​ Flexibility in discovering defects without detailed scripts

●​ Testers' creativity and knowledge leveraged
●​ Requires comprehensive written test scripts upfront
●​ Can find unexpected issues
●​ Feature interaction testing

193.​ What is the purpose of "traceability matrix"?​

Options:

●​ To ensure all requirements are covered by test cases

●​ Test script execution
●​ Defect prioritization
●​ Automation framework
●​ User access control

194.​ What is "statement coverage"?​

Options:

●​ Percentage of source code statements executed by tests

●​ Number of test scripts automated
●​ Defects per line of code
●​ Test case execution time
●​ Number of testers

195.​ What does "branch coverage" ensure?​

Options:

●​ All possible branches (true/false) in decision points are tested

●​ Load testing coverage
●​ Security testing coverage
●​ UI element coverage
●​ Regression test coverage
196.​ What is "boundary value analysis"?​
Options:

●​ Testing at the edges of input domain where defects often occur

●​ Random data testing
●​ Performance measurement
●​ Automated testing
●​ Interface testing

197.​ What is the goal of "usability testing"?​

Options:

●​ Assess ease of use and user satisfaction

●​ Load handling
●​ Security testing
●​ Automation script success
●​ Defect logging

198.​ What is a "test scenario"?​

Options:

●​ High-level test objective describing a functionality to be tested

●​ Automated script
●​ Defect report
●​ Test environment setup
●​ Test automation framework

199.​ What distinguishes "acceptance testing"?​

Options:

●​ Verification by end users to determine if software meets their needs

●​ Developer unit testing
●​ Automated test execution
●​ Performance testing
●​ Security assessment

200.​ What is the purpose of "test closure" activities?​

Options:

●​ Archive all testware, create test summary reports, and gather lessons learned
●​ Write test cases
●​ Execute regression suites
●​ Perform manual testing
●​ Run load tests
201.​ What are the key steps involved in Risk-Based Testing?​
Options:

●​ Identify risk items, assess probability and impact, prioritize tests accordingly
●​ Automate all test cases quickly
●​ Execute only manual test cases
●​ Test only functional requirements
●​ Write test scripts for all features

202.​ What is Fuzz Testing used for?​

Options:

●​ To test with invalid, unexpected, or random inputs to uncover system vulnerabilities

●​ Load testing
●​ Security certification
●​ Usability testing
●​ Smoke testing

203.​ Name one advantage of the Agile testing methodology.​

Options:

●​ Early and continuous testing with frequent feedback

●​ Testing only at the end of development
●​ No documentation required
●​ Testing all features at once
●​ Test automation only

204.​ What is the purpose of a Test Stub in top-down integration testing?​

Options:

●​ Simulate lower-level modules not yet integrated

●​ Simulate higher-level modules
●​ Automate test execution
●​ Log defects
●​ Manage test data

205.​ Which software testing technique utilizes state transition diagrams?​

Options:

●​ State Transition Testing

●​ Boundary Value Analysis
●​ Equivalence Partitioning
●​ Decision Table Testing
●​ Usability Testing
206.​ How does Pairwise Testing optimize testing?​
Options:

●​ Test all possible pairs of input combinations to reduce test cases

●​ Run two tests at the same time
●​ Pair testers for faster coverage
●​ Execute regression tests twice
●​ Parallel automation

207.​ What is the main goal of Use Case Testing?​

Options:

●​ Validate the system behavior from an end-user perspective

●​ Test internal code logic
●​ Run automation scripts
●​ Measure performance
●​ Validate security controls

208.​ What type of test design technique partitions inputs into classes?​
Options:

●​ Equivalence Class Partitioning

●​ Boundary Value Analysis
●​ Error Guessing
●​ Exploratory Testing
●​ Security Testing

209.​ What is the difference between Smoke Testing and Sanity Testing?​
Options:

●​ Smoke testing checks basic system stability; sanity testing verifies specific functionality
after changes
●​ Both are the same
●​ Sanity testing is automated; smoke testing is manual
●​ Smoke testing is performed at end-user level
●​ Sanity testing tests performance

210.​ Which testing activity is performed first in the testing life cycle?​
Options:

●​ Test Planning
●​ Test Execution
●​ Defect Reporting
●​ Test Closure
●​ Test Automation
211.​ What is test automation "maintenance"?​
Options:

●​ Updating automated tests to keep them in sync with application changes

●​ Writing new test plans
●​ Executing test cases
●​ Logging defects
●​ Scheduling automation runs

212.​ What role does "test coverage" play in assessing test completeness?​
Options:

●​ Indicates percentage of code or requirements exercised by tests

●​ Counts lines of code
●​ Monitors defect rate
●​ Tracks automation scripts
●​ Records test case count

213.​ Which test design technique focuses on testing boundary inputs?​

Options:

●​ Boundary Value Analysis

●​ Equivalence Partitioning
●​ Exploratory Testing
●​ Security Testing
●​ Error Guessing

214.​ What is a "flaky test" in automation?​

Options:

●​ A test that fails intermittently without code changes

●​ A test that always passes
●​ A test case with no defects
●​ Performance test
●​ Security test

215.​ What is the benefit of integrating automated tests in Continuous Integration?​

Options:

●​ Provides immediate feedback on code changes

●​ Removes manual testing permanently
●​ Accelerates code writing
●​ Replaces developers with testers
●​ No manual intervention possible
216.​ What is the difference between Verification and Validation in testing?​
Options:

●​ Verification ensures the product is built right; validation ensures the right product is built
●​ Both mean the same
●​ Verification is done manually; validation is automated
●​ Verification is post-release; validation is pre-release
●​ Verification tests UI; validation tests backend

217.​ What is the purpose of a traceability matrix?​

Options:

●​ Map requirements to test cases to ensure coverage

●​ Track defect status
●​ Automate test execution
●​ Manage test environments
●​ Document user requirements

218.​ Which test type is performed to check software accessibility for users with
disabilities?​
Options:

●​ Accessibility Testing
●​ Load Testing
●​ Security Testing
●​ Functional Testing
●​ Integration Testing

219.​ What does "test closure" include?​

Options:

●​ Archiving test artifacts and reporting lessons learned

●​ Writing test cases
●​ Conducting regression tests
●​ Automating test cases
●​ Scheduling next release

220.​ What is the main goal of recovery testing?​

Options:

●​ Verify software can recover after failures or crashes

●​ Test system usability
●​ Validate performance under high load
●​ Check security weaknesses
●​ Automate regression tests
221.​ What is the difference between negative testing and positive testing?​
Options:

●​ Negative testing uses invalid inputs to check error handling; positive testing uses valid
inputs to verify correct behavior
●​ Negative testing is manual; positive testing is automated
●​ Negative testing is done by developers; positive testing by testers
●​ No difference
●​ Negative testing tests UI; positive testing tests backend

222.​ What is a "stub" used for in integration testing?​

Options:

●​ Simulate lower-level modules not yet integrated

●​ Record defects
●​ Automate test cases
●​ Manage test environments
●​ Execute load tests

223.​ When should automated testing be preferred over manual testing?​

Options:

●​ For repetitive, regression, and large data-driven tests

●​ For usability testing
●​ When precise user experience is needed
●​ For exploratory testing
●​ Only for security tests

224.​ What is the primary goal of performance testing?​

Options:

●​ To evaluate software responsiveness, stability, and scalability under varying load

●​ To find UI bugs
●​ To check security vulnerabilities
●​ To automate test cases
●​ To write regression tests

225.​ Which testing level focuses on individual components or modules?​

Options:

●​ Unit Testing
●​ Integration Testing
●​ System Testing
●​ Acceptance Testing
●​ Regression Testing
226.​ What is the purpose of a bug tracking tool?​
Options:

●​ To log, track, and manage defects throughout the life cycle

●​ To automate test execution
●​ To write test cases
●​ To design UI
●​ To schedule releases

227.​ What does "test data generation" mean?​

Options:

●​ Creating data necessary to execute test cases

●​ Scheduling tests
●​ Logging defects
●​ Automating scripts
●​ Preparing the test plan

228.​ What is "test script" in automation?​

Options:

●​ A coded set of instructions to perform testing automatically

●​ Manual checklists
●​ Defect logs
●​ Test plans
●​ Requirement documents

229.​ What is the role of "test environment" in testing?​

Options:

●​ Provides hardware, software, and network setup for testing activities

●​ Manages defects
●​ Creates automation scripts
●​ Plans test cases
●​ Reviews requirements

230.​ What does "equivalence class partitioning" achieve?​

Options:

●​ Reduces total test cases by grouping similar input values into classes
●​ Manages development teams
●​ Automates testing
●​ Enhances performance
●​ Logs defects
231.​ What is "fault injection testing"?​
Options:

●​ Introducing errors intentionally to test robustness and recovery

●​ Running boundary tests
●​ Automated regression
●​ Load testing
●​ Security testing

232.​ What is the meaning of "test readiness"?​

Options:

●​ Status indicating all prerequisites are met before testing starts

●​ Completion of defects
●​ Automated test completion
●​ User acceptance
●​ Project planning

233.​ Which document defines entry and exit criteria for testing phases?​
Options:

●​ Test Plan
●​ Defect Report
●​ Test Case Specification
●​ Test Summary Report
●​ Traceability Matrix

234.​ What role does "static testing" play?​

Options:

●​ Early defect detection via reviews and walkthroughs without code execution
●​ Automated testing
●​ Regression testing
●​ Load testing
●​ Security scanning

235.​ What is defect priority?​

Options:

●​ The urgency with which a defect should be fixed

●​ Severity level
●​ Number of occurrences
●​ Test case number
●​ Defect source
236.​ What is "test closure report"?​
Options:

●​ Summary document of all testing activities, results, and lessons learned

●​ Test case documents
●​ Automation scripts
●​ Test environments
●​ Defect logs

237.​ What is the difference between severity and priority?​

Options:

●​ Severity refers to impact; priority refers to fixing urgency

●​ Both are the same
●​ Severity is time to fix; priority is cost
●​ Severity is developer assigned; priority is tester assigned
●​ No difference

238.​ What is "exploratory testing" best suited for?​

Options:

●​ Discovering defects without detailed scripts using tester experience

●​ Performance testing
●​ Regression testing
●​ Automation scripting
●​ Load testing

239.​ Why is "test coverage" important?​

Options:

●​ Ensures sufficient parts of the system are tested

●​ Helps automate more tests
●​ Speeds up testing
●​ Reduces test effort
●​ Defect prioritization

240.​ Describe "path coverage"?​

Options:

●​ Testing all possible paths through code logic

●​ Testing UI flows
●​ Automation paths
●​ Load paths
●​ Security paths
241.​ What is "test data masking"?​
Options:

●​ Protect sensitive information by obscuring data in testing environments

●​ Generate random data
●​ Automate testing
●​ Log defects
●​ Schedule tests

242.​ What is "boundary testing"?​

Options:

●​ Testing edge values of input domain where errors frequently appear

●​ Stress testing
●​ Security testing
●​ Usability testing
●​ Automation testing

243.​ Which testing verifies software's scalability?​

Options:

●​ Load Testing
●​ Functional Testing
●​ Security Testing
●​ Usability Testing
●​ Unit Testing

244.​ What is the purpose of "test estimation"?​

Options:

●​ Approximate effort and time needed for testing activities

●​ Finding defects
●​ Logging bugs
●​ Automating test scripts
●​ Planning sprint

245.​ What is "fault tolerance"?​

Options:

●​ Ability of software to continue operation despite faults

●​ Defect density
●​ Test case complexity
●​ Automation success percentage
●​ Severity index
246.​ Which is an example of "non-functional testing"?​
Options:

●​ Performance Testing
●​ Unit Testing
●​ Integration Testing
●​ User Acceptance Testing
●​ Regression Testing

247.​ What does "alpha testing" mean?​

Options:

●​ Internal acceptance testing before beta release

●​ End user testing
●​ Automated testing
●​ Load testing
●​ Security testing

248.​ What is "beta testing"?​

Options:

●​ Final testing performed by limited external users before release

●​ Internal testing by developers
●​ Automated tests
●​ Usability review
●​ Performance monitoring

249.​ What is the "test summary report"?​

Options:

●​ Final document summarizing testing results and recommendations

●​ Test case archive
●​ Test plan
●​ Automation report
●​ Defect log

250.​ What is "continuous testing"?​

Options:

●​ Executing automated tests as part of the software delivery pipeline

●​ Manual testing
●​ Security audit
●​ Test case writing
●​ User feedback
251.​ When is automated testing most beneficial over manual testing?​
Options:

●​ When tests are repetitive, require precision, or run across multiple environments
●​ For testing new and exploratory features only
●​ For usability testing and UI feedback
●​ For ad hoc testing only
●​ When human judgment is required

252.​ What is "configuration management" in software testing?​

Options:

●​ The process of managing, tracking, and controlling changes to software and test
environments
●​ Writing test cases for new features
●​ Automating regression testing
●​ Monitoring user feedback
●​ Managing customer requirements

253.​ What is "test environment virtualization"?​

Options:

●​ Creating virtual test environments to simulate various hardware and software

configurations
●​ Physical setup of hardware for testing
●​ Manual setup of test tools
●​ Non-functional testing
●​ Security scanning

254.​ How does "Shift Left Testing" benefit the software development process?​
Options:

●​ Testing activities start earlier, leading to earlier defect detection and faster feedback
●​ Testing conducted only at the end of development
●​ Automation scripts run only after release
●​ Security testing delayed till production
●​ User acceptance testing pushed forward

255.​ What is the purpose of "pair programming" in testing and development?​

Options:

●​ Two developers work together on code to improve quality and catch defects early
●​ Two testers run tests simultaneously
●​ Automated test scripts run in pairs
●​ Two environments tested simultaneously
●​ Two teams working independently
256.​ What is "mutation testing"?​
Options:

●​ Testing that intentionally modifies code to check if tests detect the changes
●​ Load testing
●​ Security testing
●​ Usability testing
●​ Automation testing

257.​ What is "test-driven development" (TDD)?​

Options:

●​ Writing tests before code to ensure requirements drive development

●​ Testing after full code completion
●​ Manual testing of UI
●​ Automated performance tests
●​ Regression testing only

258.​ What is "exploratory testing"?​

Options:

●​ Concurrent test design and execution without predefined scripts leveraging tester
knowledge
●​ Automated scripted testing
●​ Load testing
●​ Security scanning
●​ Regression testing

259.​ Which documentation is crucial in Agile testing?​

Options:

●​ User stories and acceptance criteria

●​ Detailed test plans only
●​ Defect reports only
●​ Automation scripts only
●​ Performance metrics

260.​ What is "smoke testing"?​

Options:

●​ Quick checklist of tests to verify basic stability post-build

●​ Full regression testing
●​ Load testing under peak users
●​ Usability testing
●​ Security audit
261.​ What is the goal of "sanity testing"?​
Options:

●​ Verify that specific functionality works after code changes before deeper testing
●​ Full test suite execution
●​ Automation framework development
●​ Performance testing
●​ User acceptance testing

262.​ What is a "defect life cycle"?​

Options:

●​ Process a defect follows from identification through resolution and closure

●​ Creation of test cases
●​ Execution of test plans
●​ User feedback collection
●​ Automation script management

263.​ What does "test coverage" indicate?​

Options:

●​ Percentage of code or requirements exercised by tests

●​ Number of testers
●​ Defects found count
●​ Test execution time
●​ Test plan completeness

264.​ What is "root cause analysis" in defect management?​

Options:

●​ Determining the underlying cause of defects to prevent recurrence

●​ Logging defects
●​ Scheduling tests
●​ Test automation
●​ User feedback

265.​ What is "user acceptance testing" (UAT)?​

Options:

●​ Testing conducted by end users to validate software meets business needs

●​ Automated testing
●​ Performance testing
●​ Security testing
●​ Unit testing
267.​ What are the seven principles of software testing?​
Options:

●​ Absence of errors fallacy, testing shows presence of errors, exhaustive testing not
possible, defect clustering, pesticide paradox, early testing, testing is context-dependent
●​ Waterfall, Agile, Spiral, V-Model, Incremental, Extreme, DevOps
●​ Manual, Automated, Regression, Smoke, Sanity, Load, Stress
●​ Static, Dynamic, Unit, Integration, System, Acceptance, Beta testing
●​ Functional, Non-functional, Performance, Usability, Security, Compatibility, Regression

268.​ Describe the defect life cycle.​

Options:

●​ It represents the process a defect goes through from identification to closure

●​ It is the way defects are logged in the system
●​ It tracks the test cases execution
●​ It schedules test scripts
●​ It is the automation process

269.​ What is boundary value analysis (BVA)?​

Options:

●​ Testing inputs at their minimum, maximum, just inside/outside boundaries, typical and
error values
●​ Testing all valid inputs only
●​ Testing security features
●​ Automation technique
●​ Performance testing

270.​ What is the difference between verification and validation in software testing?​
Options:

●​ Verification checks if the product is built right; validation checks if the right product is
built
●​ Both mean the same
●​ Verification is manual; validation is automated
●​ Verification is done by testers; validation by developers
●​ Validation is done first

271.​ What is the purpose of test case design?​

Options:

●​ To create detailed tests that cover specified requirements

●​ To automate all tests
●​ To log defects
●​ To plan the project schedule
●​ To manage resources

272.​ Which of the following is NOT part of static testing?​

Options:

●​ Code review
●​ Walkthrough
●​ Functional testing
●​ Inspection
●​ Peer review

273.​ Name a commonly used automated test framework for web applications.​
Options:

●​ Selenium
●​ JIRA
●​ Jenkins
●​ Postman
●​ Bugzilla

274.​ What is black-box testing?​

Options:

●​ Testing based on inputs and outputs without knowledge of internal code

●​ Testing internal code logic
●​ Automated regression testing
●​ Load testing
●​ Performance testing

275.​ What is white-box testing?​

Options:

●​ Testing internal code structure and logic

●​ Testing user interfaces
●​ Load testing
●​ Security testing
●​ Usability testing

276.​ What is regression testing?​

Options:

●​ Testing existing features after changes/modifications

●​ First round of functional testing
●​ Performance testing
●​ Security test
●​ Usability test
277.​ How does exploratory testing differ from scripted testing?​
Options:

●​ Exploratory testing is simultaneous test design and execution without scripts; scripted
testing follows predefined cases
●​ Both are the same
●​ Exploratory is automated; scripted is manual
●​ Scripted is for security; exploratory for performance
●​ Exploratory is performed only at end

278.​ What is a test scenario?​

Options:

●​ High-level description of functionality to test

●​ Automated test script
●​ Defect report
●​ Test environment setup
●​ Test closure document

279.​ What is alpha testing?​

Options:

●​ Internal acceptance testing before release

●​ Testing by end users
●​ Load testing
●​ Security testing
●​ Automated regression

280.​ What is beta testing?​

Options:

●​ Testing conducted by limited external users before final release

●​ Internal developer testing
●​ Unit testing
●​ Security audit
●​ Performance monitoring

281.​ Define "test automation".​

Options:

●​ Using software tools to execute tests automatically and verify results

●​ Manual testing by human testers
●​ Writing test scripts
●​ Logging defects
●​ Planning test cycles
282.​ What is the purpose of test planning?​
Options:

●​ Define scope, objectives, approach, resources, schedule, and deliverables

●​ Execute test cases
●​ Write automation scripts
●​ Log defects
●​ Manage risks

283.​ What is a test case?​

Options:

●​ A documented set of conditions, actions, and expected results to verify a feature

●​ Defect report
●​ Automation script
●​ Test plan
●​ User guide

284.​ What is the role of a test lead?​

Options:

●​ Managing and coordinating test activities, resources, and schedules

●​ Writing production code
●​ Automating tests exclusively
●​ Managing defects
●​ Setting project budgets

285.​ What is pair programming?​

Options:

●​ Two developers coding together on the same workstation to improve code quality
●​ Two testers executing tests side by side
●​ Two automation scripts running simultaneously
●​ Two modules integrated before testing
●​ Two independent test plans

286.​ What is "code instrumentation" in software testing?​

Options:

●​ The process of adding extra code to the software to monitor performance and behavior
during execution
●​ Writing additional manual test cases
●​ Logging defects in a database
●​ Automating regression tests
●​ Setting up test environments
287.​ What types of code instrumentation exist?​
Options:

●​ Source instrumentation, runtime instrumentation, and intermediate code instrumentation

●​ Manual, automated, and hybrid instrumentation
●​ Functional, security, and performance instrumentation
●​ White-box, black-box, and grey-box instrumentation
●​ Static, dynamic, and semi-dynamic instrumentation

288.​ What is the main purpose of code instrumentation?​

Options:

●​ To collect runtime information such as execution traces, timing, and resource usage for
analysis
●​ Writing test scripts
●​ Automating manual tests
●​ Managing test data
●​ User interface testing

289.​ What is a known limitation of code instrumentation?​

Options:

●​ Increased execution time and potential impact on software performance

●​ Lack of detailed logging
●​ Inability to identify defects
●​ No integration with test management tools
●​ Requires manual intervention only

290.​ How does code instrumentation help in debugging?​

Options:

●​ By providing logs and traces of code execution leading to error detection

●​ By automating defect fixing
●​ By generating test data
●​ By running load tests automatically
●​ By producing UI reports

291.​ What is "test coverage" and how is it related to instrumentation?​

Options:

●​ Test coverage measures the extent of code exercised by tests, aided by instrumentation
which collects execution data
●​ Test coverage counts defects found
●​ Test coverage refers to the number of testers assigned
●​ Test coverage is unrelated to instrumentation
●​ Test coverage is a measure of automation scripts
292.​ What are common code coverage metrics?​
Options:

●​ Statement coverage, branch coverage, function coverage, line coverage, path coverage
●​ Defect coverage, severity coverage, priority coverage
●​ Environment coverage, device coverage, network coverage
●​ Test case coverage, automation coverage, data coverage
●​ UI coverage only

293.​ What is a "test baseline"?​

Options:

●​ A formally reviewed and agreed version of a software or document that serves as a

reference for further development or testing
●​ The latest build deployed
●​ A completed test suite
●​ The defect log
●​ Test environment setup

294.​ What does a "test driver" do in bottom-up integration testing?​

Options:

●​ Simulates higher level modules to call the module under test

●​ Executes test scripts automatically
●​ Logs defects found during tests
●​ Creates test data
●​ Manages environment configurations

295.​ What is "coverage testing"?​

Options:

●​ Testing to ensure that a specified coverage criterion is met, such as code or requirements
coverage
●​ Security testing
●​ Usability testing
●​ Load testing
●​ Automated testing

296.​ What is "negative testing"?​

Options:

●​ Testing using invalid or unexpected inputs to ensure system robustness

●​ Testing valid use cases only
●​ Performance testing
●​ Security testing
●​ Regression test suite execution
297.​ Define "test data masking."​
Options:

●​ Protecting sensitive data within test sets to prevent exposure in non-production

environments
●​ Generating random test data
●​ Logging defects
●​ Automating tests
●​ Defect prioritization

298.​ What characteristic distinguishes "smoke testing"?​

Options:

●​ Quick, shallow testing to verify basic functionality and build stability

●​ In-depth functional testing
●​ Performance benchmarking
●​ Automated testing only
●​ Usability testing

299.​ What is "sanity testing"?​

Options:

●​ Verifying specific functionality after minor code changes before further testing
●​ Full system testing
●​ Load testing
●​ Security audit
●​ User acceptance testing

300.​ What is the primary goal of "acceptance testing"?​

Options:

●​ Verify the software meets business requirements and is ready for production
●​ Automated regression testing
●​ Load testing
●​ Usability testing
●​ Security scanning