Software Testing in SDLC

1. Which phase of the SDLC is software testing typically associated with?

• 1. Planning

• 1. Design

• 1. Coding

• 1. Testing

1. What is the primary goal of software testing in the SDLC?

• 1. To create software requirements

• 1. To find and fix defects in the code

• 1. To design the user interface

• 1. To document the software architecture

1. What is the purpose of regression testing in the SDLC?

• 1. To test a new feature

• 1. To ensure that previously developed and tested software still works after changes

• 1. To validate the system against the requirements

• 1. To test the entire software system in one go

1. Which testing technique involves testing the software from the perspective of an end user?

• 1. White-box testing

• 1. Black-box testing

• 1. Grey-box testing

• 1. Alpha testing

1. What is the primary focus of acceptance testing?

• 1. Validating individual units of code

• 1. Verifying system integration

• 1. Ensuring compliance with coding standards

• 1. Validating that the software meets specified requirements

1. Which of the following is not a common type of software testing?

• 1.  Performance Testing

• 1. Usability Testing

• 1. Documentation Testing

• 1. Load Testing

1. What is the primary purpose of exploratory testing?

• 1. To follow a predetermined set of test cases

• 1. To simulate real-world user scenarios

• 1. To discover defects by exploring the software

• 1. To automate repetitive testing tasks

1. Which type of testing is typically performed by developers on their own code before it is integrated into the main codebase?

• 1. Integration Testing

• 1. System Testing

• 1. Unit Testing

• 1. Regression Testing

1. What is the primary focus of usability testing?

• 1. Validating individual units of code

• 1. Verifying system integration

• 1. Assessing the software's user-friendliness

• 1. Ensuring compliance with coding standards

  2. Identifying and fixing defects in the code

1. What is the purpose of load testing in the SDLC?

• 1. To verify the software against requirements

• 1. To simulate real-world user scenarios

• 1. To identify and mitigate security vulnerabilities

• 1. To test the software's ability to handle expected loads