Coding, Implementation, and Testing : MCQs & PYQs with Explanation

Option C

In the software testing process, System Testing is generally used as an acceptance test because it evaluates the complete and integrated software system as a whole. 
At this stage, the system is tested against the specified requirements to ensure that it behaves correctly in a real-world environment before being delivered to the user.
System testing verifies all functional and non-functional requirements and is usually the last level of testing before acceptance by the client.

Option A

In Integration Testing, modules are tested by combining them step by step. Sometimes, required modules are not yet developed, so we use Stubs and Test Drivers to simulate missing parts.

• Top-Down Testing: Testing starts from the top module or main module and goes downward. Lower-level modules may be missing, so Stubs are used to simulate them.
• Bottom-Up Testing: Testing starts from lower-level modules. Higher-level modules may be missing, so Test Drivers are used to simulate them.

Option A

The Unit Testing verifies the functionality of individual components or functions in isolation.

Option C

Cyclomatic complexity tells us how many independent paths exist in a program. Here, graph has 17 edges and 13 nodes, there are 6 independent paths that must be tested to cover all possible branches in the logic.
Cyclomatic Complexity (V(G)) :
V(G)=E−N+2
Where:
E is number of edges given as 17.
N is number of nodes given as 13. 
So, 
V(G) = 17−13+2
V(G) = 6

Option B

Option D

Control structure testing is a type of White-Box testing that focuses on the logical control structures of a program, such as decisions, loops, and conditions, to ensure that all possible execution paths are tested. It includes techniques like, condition testing, data flow testing, Loop testing etc.

The Graph-Based Testing does not belong to control structure testing. It falls under Black-Box testing techniques, where the focus is on relationships between inputs, outputs, and modules rather than internal control flow.

Option D

Fault-Based Testing techniques are designed to evaluate how well a software system can handle errors or faults. The idea is to intentionally introduce faults and check whether the testing process can detect them.
Mutation Testing is a well-known fault-based testing technique. It involves making small modifications (called mutants) to the program’s source code intentionally, to check if the existing test cases can detect these faults.

Option C

The Integration Testing ensures that modules or components work together correctly after individual unit testing.

Option A

When software is developed as a product for many users, developers use Alpha and Beta Testing to find errors that only real users can detect. These tests are performed after internal testing to ensure the software works well in real-world conditions.

• Alpha Testing is done internally by developers and testers within the organization to catch major issues early.
• Beta Testing is done by actual users outside the organization to find hidden bugs and get real user feedback before the final release.

Option C

In unit testing, the extra supporting code written to test modules is collectively called scaffolding. It is a general term that includes all the auxiliary code required for testing. Scaffolding includes:

• Drivers to call the module.
• Stubs to simulate missing modules.

Note:
Scaffolding is the standard software engineering term for all unit test support code. Covers drivers, stubs, test harnesses, mocks.

Option D

Cyclomatic Complexity (McCabe’s Complexity) measures the number of independent paths in a program. It is used to determine testing effort.
When two modules are independent, their complexities simply add. However, when modules are integrated sequentially, they are connected by a control flow, which removes one independent path. Since execution flows from one module to another.
So, for Sequential Integration: Combined Complexity = N1+N2-1

Option A

Beta Testing is the type of testing performed by end users at their own locations in a real working environment. It is carried out after alpha testing and helps identify real-world issues, usability problems, and hidden bugs before the final release of the software.

• Alpha Testing is done internally by developers and testers within the organization to catch major issues early.
• Beta Testing is done by actual users outside the organization to find hidden bugs and get real user feedback before the final release.
• Regression Testing checks whether changes break existing functionality.
• Monkey Testing involves random testing without test cases.

Option B

In a Program Graph, each node represents a statement or a decision, and an edge represents possible control flow. When we reach a node, the number of paths to that node is the sum over all its incoming edges of the number of paths along each edge.
For a control‑flow construct like if‑then‑else, any path that reaches the decision node branches into the then part or the else part. Each of these branches can then lead to multiple paths to the end node.
From the start node to M, there are x different paths. After reaching M, each of these paths can go through either the if part (y paths) or the else part (z paths). Therefore, the total number of paths after node M becomes (y+z).
Since each of the x incoming paths can combine with all possible paths after M, we multiply them. Hence, the total number of paths through node M is: x*(y+z).

Option A

Performance Testing is a software testing method used to check how efficiently a program or system works under a given workload. It focuses on basic aspects like how quickly the system responds, how much time it takes to execute functions, how many users or operations it can handle at once (throughput), and how much primary or secondary memory it consumes during execution.

• Performance testing measures speed, responsiveness, stability, and resource usage.
• It ensures the software meets specified performance criteria before deployment.

Option A

Static Testing is a type of software testing that does not require executing the code. It focuses on reviewing and analyzing the code, documentation, or design to find defects. Examples include:

• Code reviews.
• Walkthroughs.
• Inspections.
• Syntax and requirement checks.