CS Free MCQ Bank

[ 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 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.

[ Option D ]

System Testing checks the complete integrated system to ensure:

• All components work together correctly.
• The system meets functional and non-functional requirements.
• Overall performance and behavior are as expected.
   

[ Option D ]

Programmed checks help detect errors automatically during processing, improving data quality and reducing manual inspection.
In testing, programmed checks are automated controls embedded within software or batch processes to verify data integrity, correctness, and processing order. Common programmed checks include:

[ Option B ]

In software testing, the term Granularity refers to the level of detail or scope at which the software is tested. There are several recognized levels of testing techniques like unit testing, component testing, and system testing, each focusing on different parts of the system.
The Segment Testing is not a standard level of software testing. It is not formally recognized in the software testing process hierarchy.

[ Option C ]

Security Testing is generally not included in unit testing. Unit testing focuses on verifying the functionality of individual program units or components in isolation. It includes tests related to the internal structure and behavior of the unit, often through techniques like Structural Testing.

[ Option A ]

Gorilla Testing is a software testing technique that focuses heavily on testing a specific module or feature of an application. It involves intense, repetitive, and rigorous testing of one particular part to find as many defects as possible in that area. This method ensures the robustness and reliability of critical modules, uncovering hidden bugs that might be missed in broader testing.

Fuzz Testing involves providing random or invalid inputs to the software to check how it handles unexpected data.

Inter-System Testing, tests the interaction between two or more different systems to ensure they work together correctly.

Breadth Testing, focuses on testing all modules at a shallow level without going deep into any single one.

[ Option C ]

Common Software Testing Types:

[ Option B ]

Stress Testing is a type of non-functional testing that evaluates how a system behaves under extreme or abnormal conditions.

• The main goal of stress testing is to determine the breaking point of the system and to ensure that it can handle heavy load conditions without crashing or losing data. 
• It helps identify performance bottlenecks, memory leaks, or stability issues that might appear only under intense workloads.

[ Option B ]

The software testing process follows a logical and structured sequence to ensure that the program is tested accurately and efficiently.

[ Option B ]

Logical Errors (Semantic Errors) occur when the code executes without any syntax or compilation errors, but the output is not what the programmer intended. These errors arise from mistakes in the program's logic, causing it to produce incorrect or unintended results.

[ Option A ]

Software Testing is the process of evaluating a software application to check whether it meets the specified requirements and works as expected. It helps to identify defects, errors, or gaps so that they can be fixed before the product is delivered. The main goals of testing are:

• To ensure the software is reliable, accurate, and secure.
• To confirm it works correctly under different conditions.
• To improve the quality and user satisfaction of the final product.

After this, testing is usually carried out in different levels (Unit, Integration, System, Acceptance) to make sure the software is correct at every stage.

[ Option B ]

When a new module is added to a system, several things change:

• New data flow paths are created.
• New inputs and outputs appear.
• New control logic is activated.

Even if these changes are small, they can accidentally affect older parts of the system that were working perfectly earlier. To ensure that new changes do not break the existing functionality, we perform Regression Testing.
Regression Testing is a type of testing that re-checking everything to confirm nothing got disturbed.

• Checks old features to ensure they still work correctly after updates.
• Finds new errors caused by adding new modules, fixing bugs, or making modifications.
• Ensures system stability after every change.

[ Option C ]

Parallel Implementation is a strategy where the new system runs alongside the old system for a period of time. Both systems operate independently, and outputs from both are compared to ensure the new system works correctly. Once confident, the old system is discontinued.

[ Option D ]

Functional tests on a program unit are performed to check whether programs do what they are expected to do. It focuses on:

• Whether each function works correctly.
• Whether input produces the correct output.
• Whether the program behavior matches requirements.

[ Option B ]

Coding translates design specifications into working software using a programming language.

[ Option C ]

Debugging is the process of finding and fixing errors or defects in a program after they have been discovered during testing. It is different from Testing, because testing helps detect the presence of errors, while debugging helps locate and remove them.

[ Option C ]

Verification is the process of checking whether the software is being built correctly according to design documents, specifications, and plans. It focuses on ensuring that each function, logic, and module is correctly implemented before the product is completed.

Validation is the process of checking whether the final software product meets customer needs and expectations. It ensures that the system performs the intended functions in the actual working environment and satisfies all user requirements.

[ Option A ]

In the Software Development Life Cycle (SDLC), the actual programming or coding of the software is done during the development phase, which is often referred to as the "development and documentation" phase.

This phase follows the design and analysis phases and involves writing the source code based on detailed design specifications.

[ Option D ]

Code Readability is the quality of a well-written program that makes it easy for other developers to understand, modify, and maintain. Readable code is clear, logically structured, and communicates its intent, making it easier for others to work on it without confusion or errors.
THE READABLE CODE HAS:

• Clear variable and function names.
• Proper indentation.
• Comments where necessary.
• Simple and clean logic.
• Consistent coding style.

[ Option A ]

Beta Testing is a type of User Acceptance Testing (UAT) performed by external users outside the development organization. It involves releasing the nearly completed product to a select group of external users or a broader audience to gain real-world exposure and feedback. 
This helps identify issues that may not have been caught during internal testing and validates the product's usability and stability in a real environment.