Software Testing MCQ Quiz - Objective Question with Answer for Software Testing - Download Free PDF

The Correct answer is: Option 1 (D, B, E, A, C)

Key Points

• D: Level 1 - Initial: At this stage, the software process is characterized as ad-hoc, chaotic, and unpredictable. Success depends largely on individual heroics rather than stable processes.
• B: Level 2 - Repeatable: This level establishes basic project management discipline. The organization can repeat earlier successes on projects with similar applications by managing requirements, planning, and tracking.
• E: Level 3 - Defined: Processes for both management and engineering are standardized, documented, and integrated into a standard software process for the entire organization.
• A: Level 4 - Managed: The organization sets quantitative quality goals for both products and processes. Performance is measured using statistical techniques, making it predictable.
• C: Level 5 - Optimizing: The highest level focuses on continuous process improvement and innovation. The organization identifies process weaknesses and proactively strengthens them through defect prevention and technology change management.

Additional Information

• The CMM framework was developed by the Software Engineering Institute (SEI) to benchmark the maturity of an organization's development processes.
• Each level serves as a foundation for the next; organizations must achieve the goals of one level before effectively maturing to the subsequent level.

Concept

• Efficiency in a process like software testing is often measured by the reduction in time required to complete a task.
• Percentage improvement represents the ratio of the change in time to the original time, expressed as a percentage.
• A reduction in time signifies an increase in productivity or efficiency.

Formula Used

The percentage improvement (or percentage reduction in time) is calculated as:

\(\text{Percentage Improvement} = \left( \frac{\text{Initial Time} - \text{Reduced Time}}{\text{Initial Time}} \right) \times 100\)

Calculation

Given:

Initial testing time (\(T_{initial}\)) = \(20\) hours

Reduced testing time (\(T_{final}\)) = \(15\) hours

Step 1: Calculate the reduction in time:

\(\text{Reduction} = T_{initial} - T_{final}\)

\(\text{Reduction} = 20 - 15 = 5\) hours

Step 2: Calculate the percentage improvement:

\(\text{Percentage Improvement} = \left( \frac{5}{20} \right) \times 100\)

\(\text{Percentage Improvement} = 0.25 \times 100\)

\(\text{Percentage Improvement} = 25\%\)

Hence, the percentage improvement in the testing efficiency is 25%.

The correct answer is A, B, C Only.

Key Points

• Alpha testing is done at the developer's site in a controlled environment. This allows for early feedback and ensures that major issues are resolved before moving to the next phase.
• Beta testing is performed at the end-user's site, often with the developer's presence. It provides real-world feedback and identifies any remaining issues that need to be addressed.
• Acceptance testing is typically formal and can last for an extended period, such as weeks, ensuring the product meets the client's requirements and specifications.

Additional Information

• Alpha Testing:
  • Conducted internally by developers and testers.
  • Simulates real-world usage but under controlled conditions.
  • Identifies major bugs and usability issues early in the development cycle.
• Beta Testing:
  • Performed in the actual environment where the product will be used.
  • Focuses on gathering user feedback and identifying any issues overlooked during alpha testing.
  • Helps assess product performance in real-world scenarios.
• Acceptance Testing:
  • Ensures that the product meets the contractual requirements and user expectations.
  • Can involve both functional and non-functional testing.
  • Often the final step before the product is officially launched or handed over to the client.
• Important Points:
  • Alpha and beta testing serve different purposes and are not interchangeable.
  • Acceptance testing is critical for ensuring client satisfaction and project success.
  • Effective testing at each stage minimizes risks and ensures a high-quality product.

The correct answer is Both I and II

Key Points

• Statement I: White box testing is performed early in the testing phase.
  • White box testing, also known as structural or code-based testing, is performed early in the testing phase by developers or testers who have knowledge of the internal code structure.
  • It focuses on verifying the code logic, paths, and design structure before the application moves to functional testing.
• Statement II: Black box testing tends to be applied during later stages of testing.
  • Black box testing, also called functional or behavioral testing, is typically performed during the later stages of testing.
  • It does not require knowledge of the internal structure or code and focuses on testing the application's functionality against requirements.
• Since both Statement I and Statement II are correct, the correct option is Option 3: Both I and II.

Additional Information

• White Box Testing:
  • Focuses on code coverage, logic paths, and unit testing.
  • Performed by developers or testers with knowledge of the code.
• Black Box Testing:
  • Focuses on functionality, user interface, and requirements testing.
  • Performed without knowledge of the internal code structure.

The correct answer is 2) B, A, C, D

Key Points

• Unit Testing (B): ✅ Unit testing is the first level of testing in the software development lifecycle. It focuses on testing individual components or units of the software to ensure they work as expected. This is typically performed by developers.
• Integration Testing (A): ✅ After unit testing, integration testing is performed to verify the interaction between different modules or components of the software. This ensures that integrated components work together correctly.
• System Testing (C): ✅ System testing is conducted after integration testing. It evaluates the software as a whole system to ensure that it meets the specified requirements.
• Acceptance Testing (D): ✅ This is the final stage of testing in the software development lifecycle. It is performed to validate whether the software meets the business requirements and is ready for deployment. It is usually conducted by the end-users or clients.

Additional Information

• Sequence of Testing: The typical sequence followed in the software development lifecycle is:
  • 1. Unit Testing
  • 2. Integration Testing
  • 3. System Testing
  • 4. Acceptance Testing
• Purpose: This sequence ensures that issues are identified and resolved at the earliest possible stage, reducing the overall cost and effort required for fixing defects.

Hence, the correct answer is: option 2) B, A, C, D

Concept:

Mutlimedia means combination of text, audio, video, graphics, and animation. Mutlimedia project are the multimedia materials which are presented on computer screen.

Explanation:

Phases of a multimedia project are : planning, designing , testing and delivering. 

Some points about multimedia project : 

• Interactive mutlimedia gives the navigational controls to the user. It control what elements are to be delivered.
• It requires creative skills, tools and organization talent to create mutlimedia projects.
• There are two categories in multimedia : linear and non - linear.
• Linear multimedia is without any navigational control example cinema.
• Non - linear provides user interactivity to control progress. Example : computer game.
• Mutlimedia system must be integrated, handled digitally and usually interactive.
• Mutlimedia can be delivered using optical disk, web or distributed network.

NON-FUNCTIONAL REQUIREMENT (NFR)

It specifies the quality attribute of a software system. They judge the software system based on Responsiveness, Usability, Security, Portability, and other non-functional standards that are critical to the success of the software system

Product requirements

Requirements specify that the delivered product must behave in a particular way, e.g. execution speed, reliability, etc.

Organizational requirements

Requirements which are a consequence of organizational policies and procedures, e.g. process standards used, implementation requirements, etc.

External requirement

Requirements which arise from factors which are external to the system and its development process, e.g. interoperability requirements, a legislative requirement

The correct option is (4)

Gorilla testing

Concept:-

This kind of software testing methodology places a lot of emphasis on thoroughly evaluating one specific module. By having various testing teams evaluate the same capability, quality assurance teams examine one or a few functionalities fully or exhaustively to discover any deviations.

Key Points

• Gorilla testing is a method of software testing in which a program module is routinely examined to ensure that it is working correctly and is free of flaws.
• A module can be assessed in exactly the same manner 100 times. Gorilla testing is so frequently referred to as "Frustrating Testing."

Additional InformationFuzz testing:- An automated software testing technique called fuzzing introduces erroneous, abnormal, or unexpected inputs into a system in order to detect flaws and vulnerabilities in the software.

Breadth Testing:- It is a test suite that confirms a product's complete functionality but does not thoroughly evaluate all of the features.

Inter-system testing:- Inter-system testing is the process of evaluating the integration points and functionality between various systems that share a common data source.

The correct answer: Acceptance Testing

Alpha and Beta testing are forms of:

Acceptance Testing

Important Points

Alpha Testing is usually done by internal staff before the product is released to external testers. It is a type of acceptance testing that's done in a lab environment and not by the end users. It helps identify all possible issues and problems in the system before it goes for Beta testing. 

Beta Testing is performed by actual users or potential customers in their own environment. It is the second phase of testing in which a sampling of the intended audience tries the product out before it is officially released to the general public. This is the final test before shipping the product. Problems that were not discovered during Alpha testing may be identified here.

These types of tests are done to make sure that the system is working as expected and will be accepted by the end users. They are types of User Acceptance Testing (UAT) and are very important in software development processes.

Data

code testes in unit testing = t =90% = 0.9

probability of success = p = 0.9

Calculation

Reliability ≤  t × p = 0.9 ×0.9 = 0.81

Threfere, the reliability of the module is at most 0.81

Option 1 is the correct answer. Coupling in software design refers to the degree of functional interdependence between two software modules. It measures how closely related two modules are, in terms of their functionality and how much one module relies on another.

A high degree of coupling between modules means that they are closely related, and changes in one module may affect the other. In contrast, a low degree of coupling means that the modules are more independent, and changes in one module are less likely to impact the other.

Coupling can be classified into different types, such as content coupling, common coupling, control coupling, stamp coupling, and data coupling, based on the nature of the interdependence between modules.

Reducing coupling between modules is desirable because it makes the software design more modular, flexible, and easier to maintain. High coupling can make software difficult to change, test, and debug, leading to higher costs and longer development cycles.

The correct answer is [0, 1, 4000, 4001]

Key PointsBoundary Value Analysis (BVA) is a testing technique that focuses on testing the boundaries between partitions. For an input range of 1 to 4000, BVA would typically involve testing the minimum and maximum values, as well as just below and just above these boundaries.

Given the range of 1 to 4000, the boundary values to consider are:

• The minimum value in the range: 1
• Just below the minimum value: 0
• The maximum value in the range: 4000
• Just above the maximum value: 4001

Therefore, the test values that cover these boundaries are: 4) [0, 1, 4000, 4001].

Correct answer is Option 4

Explanation:

• Fault-based testing aims to detect certain classes of known faults.
• Example: security testing for buffer overflows
• Mutation Testing Fault-based testing strategy
• It is used to evaluate test suite adequacy
• Measures the effectiveness of test cases
• Leads to creation of more effective tests
• Mutation Testing Faults are introduced into the program by creating versions of the program called mutants.

Debugger:

• A debugger is a computer program used to test and debug target programs.
• The main use of a debugger is to run the target program under controlled conditions that permit the programmer to track its operations in progress and monitor changes in computer resources that may indicate malfunctioning code.
• Typical debugging facilities include the ability to run or halt the target program at specific points, display the contents of memory, CPU registers or storage, and modify memory or register contents in order to enter selected test data that might be a cause of faulty program execution.

Important Points

Thread testing

Thread Testing is one such type of software testing that is usually conducted during the early stages of System Integration Testing. This type of software testing technique is immensely useful in scenarios where an application is of a type that uses a client-server architecture. Thread testing is a vital part of integration testing and is usually performed for testing real-time systems. The main focus of this type of testing is to check the data communication amongst the multiple modules coded by different programmers.

Additional Information

Bottom-up testing

It is an approach to integrated testing where the lowest level components are tested first, then used to facilitate the testing of higher-level components. The process is repeated until the component at the top of the hierarchy is tested.

Back-to-back testing

It is a type of testing which is conducted if there are two or more variants of components with similar functionality. It is also called Comparison Testing. The aim of back-to-back testing is to compare the results to check if there are any divergences in the work.

Top-down testing 

It is an integration testing technique used in order to simulate the behaviors of the lower-level modules that are not yet integrated. Stubs are the modules that act as temporary replacement for a called module and give the same output as that of the actual product.

Hence Option 4 is correct