The four test levels used in ISTQB syllabus are: 1. Component (unit) testing 2. Integration testing 3. System testing 4. Acceptance testing An organization wants to do away with integration testing…

Question

Options

• AIt is allowed as organizations can decide on men test levels to do depending on the context of the
• BIt is allowed because integration testing is not an important test level arc! can be dispensed with.
• CIt is not allowed because integration testing is a very important test level and ignoring i: means
• DIt is not allowed as organizations can't change the test levels as these are chosen on the basis of

• A
  7% (2)
• B
  14% (4)
• C
  4% (1)
• D
  75% (21)

Explanation

The V-model is a software development life cycle model that defines four test levels that correspond to four development phases: component (unit) testing with component design, integration testing with architectural design, system testing with system requirements, and acceptance testing with user requirements. The V-model emphasizes the importance of verifying and validating each phase of development with a corresponding level of testing, and ensuring that the test objectives, test basis, and test artifacts are aligned and consistent across the test levels. Therefore, an organization that wants to follow the V-model cannot do away with integration testing, as it would break the symmetry and completeness of the V-model, and compromise the quality and reliability of the software or system under test. Integration testing is a test level that aims to test the interactions and interfaces between components or subsystems, and to detect any defects or inconsistencies that may arise from the integration of different parts of the software or system. Integration testing is essential for ensuring the functionality, performance, and compatibility of the software or system as a whole, and for identifying and resolving any integration issues early in the development process. Skipping integration testing would increase the risk of finding serious defects later in the test process, or worse, in the production environment, which would be more costly and difficult to fix, and could damage the reputation and credibility of the organization.

No community discussion yet for this question.