All Free Software Engineering MCQs with Answers

• A. Integration testing
• B. Unit testing
• C. Completion of Testing
• D. Regression Testing

Explanation: Unit testing is normally performed alongside coding because each newly written unit can be checked in isolation before integration.

• A. instantaneous test group
• B. integration testing group
• C. individual testing group
• D. independent test group

Explanation: ITG commonly means Independent Test Group, a group separate from the developers that performs testing to provide greater objectivity.

• A. A representative sample of tests that will exercise all software functions
• B. Additional tests that focus on software functions that are likely to be affected by the change
• C. Tests that focus on the software components that have been changed
• D. Low-level components are combined into clusters that perform a specific software sub-function

Explanation: Regression testing reruns representative tests and tests areas changed or likely to be affected by a modification.

• A. Alpha Testing
• B. Beta Testing
• C. Validation Testing
• D. Both Alpha and Beta

Explanation: Alpha and beta testing both involve evaluating the software from the user or customer perspective, with beta testing typically taking…

• A. Failure intensity
• B. Testing time
• C. Metrics
• D. All of the mentioned

Explanation: Testing metrics, such as failure intensity and test coverage, provide evidence for deciding when further testing has diminishing value.

• A. White box testing
• B. Black box testing
• C. Grey box testing
• D. None of the mentioned

Explanation: Behavioral testing examines what the software does from its externally observable behavior, without requiring knowledge of its internal…

• A. User's end
• B. Developer's end
• C. User's & Developer's end
• D. None of the mentioned

Explanation: Beta testing is performed by actual or representative users in the user environment, after the developer's alpha testing.

• A. Software Process Improvement and Compatibility Determination
• B. Software Process Improvement and Control Determination
• C. Software Process Improvement and Capability Determination
• D. None of the mentioned

Explanation: SPICE expands to Software Process Improvement and Capability Determination, the framework associated with assessing and improving…

• A. Basic path testing
• B. Boundary value analysis
• C. Code path analysis
• D. None of the mentioned

Explanation: Boundary value analysis tests inputs at and around their limits without examining the program's internal code, making it a black-box…

• A. Users
• B. Developers
• C. Customers
• D. None of the mentioned

Explanation: Unit tests target individual functions, classes, or modules, whose internal behavior is best understood by the developers who implement…

• A. Black box testing
• B. Performance testing
• C. Unit testing
• D. None of the mentioned

Explanation: Performance testing measures qualities such as response time, throughput, and scalability rather than checking a specific business…

• A. Unit testing
• B. Regression testing
• C. Adhoc testing
• D. None of the mentioned

Explanation: Ad hoc testing is informal and unscripted, commonly carried out without a defined plan or test documentation.

• A. Developer's end
• B. User's end
• C. Developer's & User's end
• D. None of the mentioned

Explanation: Alpha testing is conducted under the developer's control, usually at the developer's site, before the product is released to external…

• A. Unit Testing
• B. System Testing
• C. Integration Testing
• D. All of the mentioned

Explanation: The standard testing levels include unit testing, integration testing, and system testing, with acceptance testing often added as the…

• A. Retesting
• B. Sanity testing
• C. Breadth test and depth test
• D. Confirmation testing

Explanation: Maintenance testing commonly uses breadth testing to check the wider impact of a change and depth testing to examine the changed area in…

• A. Black box testing
• B. White box testing
• C. Red box testing
• D. Green box testing

Explanation: White-box testing examines the internal code, including statements, branches, and paths.

• A. White Box Testing
• B. Black Box Testing
• C. White Box & Black Box Testing
• D. None of the mentioned

Explanation: Boundary value analysis is a black-box technique that tests values at and around input limits, where defects commonly occur.

• A. Statement Testing
• B. Decision Testing
• C. Condition Coverage
• D. All of the mentioned

Explanation: Statement testing, decision testing, and condition coverage all examine elements of the program's internal structure.

• A. Design based testing
• B. Structural testing
• C. Error guessing technique
• D. None of the mentioned

Explanation: White-box testing is also called structural or code-based testing because it derives test cases from the program's internal structure.

• A. Black box testing
• B. White box testing
• C. Yellow box testing
• D. Green box testing

Explanation: Cyclomatic complexity measures the number of independent execution paths through source code, using the program's control-flow structure.