BCS CTFL4 Exam - Topic 4 Question 23 Discussion

Actual exam question for BCS's CTFL4 exam

Question #: 23
Topic #: 4

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 but otherwise follow V-model. Which of the following statements is correct?

AIt is allowed as organizations can decide on men test levels to do depending on the context of the system under test

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 definite poor product quality

DIt is not allowed as organizations can't change the test levels as these are chosen on the basis of the SDLC (software development life cycle) model

Show Suggested Answer

Suggested Answer: D

In Agile teams, close collaboration among testers and other team members can lead to organizational risks such as: ii . Close interaction with developers causes a loss of the appropriate tester mindset. iv . Testers, once they have acquired technical development or business skills, leave the testing team.

These risks highlight the potential issues of diminished testing perspective and team turnover when testers integrate closely with developers and other roles.

by Flo at Feb 07, 2025, 02:27 PM

Limited Time Offer

25%

Off

Get Premium CTFL4 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Junita

4 months ago

No way they can skip integration testing, that’s just asking for trouble!

upvoted 0 times

...

Mitsue

5 months ago

Organizations can adapt testing levels based on their needs, right?

upvoted 0 times

...

Lettie

5 months ago

I thought integration testing was optional? Surprised to hear it’s so important!

upvoted 0 times

...

Elmer

5 months ago

Totally agree, skipping it sounds risky.

upvoted 0 times

...

Emmett

5 months ago

Integration testing is crucial for catching issues early!

upvoted 0 times

...

Renea

5 months ago

I’m not sure if the V-model is strict about test levels, but I recall something about them being based on the SDLC, which might mean they can’t just skip integration testing.

upvoted 0 times

...

Rodolfo

6 months ago

I think I saw a practice question that emphasized the importance of each test level, especially integration testing, so I’m leaning towards it being necessary.

upvoted 0 times

...

Lashon

6 months ago

I feel like I studied something about organizations having flexibility in their testing approach, but I'm not entirely sure how that applies here.

upvoted 0 times

...

Magda

6 months ago

I remember that integration testing is crucial for finding issues between components, so I think it might be important to keep it in the process.

upvoted 0 times

...

Bok

6 months ago

Okay, let me review the test levels again. I think the key here is understanding how the V-model works and why integration testing is a required step.

upvoted 0 times

...

Dell

6 months ago

I'm pretty confident that option C is the correct answer. Integration testing is essential, and the organization can't just decide to skip it.

upvoted 0 times

...

Erick

6 months ago

Hmm, I'm a bit confused here. Isn't integration testing a crucial part of the V-model? Skipping it seems risky.

upvoted 0 times

...

Sabina

6 months ago

This is a tricky one. I'll need to think carefully about the importance of integration testing and how it fits into the V-model.

upvoted 0 times

...

Leonora

12 months ago

Seriously, who comes up with these options? It's like they've never heard of the importance of testing the interactions between different parts of the system. Skipping integration testing is just begging for trouble.

upvoted 0 times

Danilo

10 months ago

I see your point, but I still think integration testing is crucial for overall system quality.

upvoted 0 times

...

Aja

11 months ago

A) It is allowed as organizations can decide on men test levels to do depending on the context of the system under test

upvoted 0 times

...

Salome

11 months ago

I agree, skipping integration testing can lead to serious issues down the line.

upvoted 0 times

...

Mary

11 months ago

C) It is not allowed because integration testing is a very important test level and ignoring it means definite poor product quality

upvoted 0 times

...

Jeff

12 months ago

Hah, that's a bold move, trying to skip integration testing. I'd like to see them try that and then explain to the client why their software is falling apart at the seams.

upvoted 0 times

...

Elouise

12 months ago

Hmm, I'm not sure I agree with option B. Integration testing may not be the most glamorous part of the process, but it's essential for ensuring the different components work together seamlessly.

upvoted 0 times

Karan

11 months ago

User 2: I think we should stick to the test levels outlined in the syllabus to ensure a thorough testing process.

upvoted 0 times

...

Ardella

11 months ago

User 1: I agree with you, integration testing is crucial for the overall quality of the product.

upvoted 0 times

...

Rueben

12 months ago

Ah, I see they're trying to trick us here. Integration testing is a crucial step in the V-model, you can't just skip it! That's like trying to build a house without laying the foundation.

upvoted 0 times

...