Module 5: Testing throughout the Software Lifecycle

Which of the following represents the correct sequence of phases in a typical Software Life Cycle?

• Coding → Design → Requirements Analysis → Testing → Maintenance

• Requirements Analysis → Design → Coding → Testing → Installation → Maintenance

• Maintenance → Coding → Testing → Design → Requirements Analysis

• Testing → Coding → Requirements Analysis → Design → Installation

What is the primary purpose of Component Testing?

• To verify system behaviour as a whole

• To test individual components of an application independently

• To validate intercommunications between systems

• To test the software’s acceptance by the user

In Component Testing, what is a ‘Stub’?

• A tool for automated testing

• A component used to test another component when parts are missing

• A type of defect report

• A final system deliverable

System Testing primarily checks:

• Individual modules of the software

• Entire system behavior according to requirements

• User interface aesthetics

• Only functional specifications, not non-functional ones

What does System Integration Testing (SIT) focus on?

• Testing each component individually

• Verifying intercommunications between diverse systems

• Running performance tests under extreme loads

• Acceptance of the software by the end user

Which of the following is true about Acceptance Testing?

• It occurs before system testing

• Its goal is to check if the software meets specifications

• It is performed by developers only

• It replaces the need for system testing

Alpha Testing is usually conducted:

• By end-users in their own environment

• At the developer’s site before release

• During regression testing

• After Beta Testing

Non-Functional Testing includes:

• Checking menu functions and text input

• Assessing system attributes like performance and reliability

• Verifying code syntax

• Acceptance by business users

What is the main difference between Retesting and Regression Testing?

• Retesting checks previously passed test cases; Regression checks failed cases

• Retesting verifies specific failed test cases; Regression checks if changes introduce new issues

• Retesting is automated; Regression is always manual

• Retesting occurs after Regression Testing

Stress Testing is used to:

• Measure system usability

• Determine the robustness of a system under extreme loads

• Test only functional requirements

• Verify correctness of individual components