Q: 10
Which of the following could be a disadvantage of independent testing?
Options
Discussion
D imo, because when testing is done independently, devs might start thinking quality's not really their problem. I think that's the main disadvantage ISTQB is pointing at here instead of things about speed or overlap.
D stands out because if testing is always seen as 'someone else’s job,' devs might slack off on quality. I’ve seen ISTQB mention this risk before. Not 100% but fits best in their context, right?
D , ISTQB materials and practice exams always flag developer ownership of quality as the downside with independent testing. Saw this in the official guide, too.
Yeah, D fits what ISTQB warns about. If independent testers always handle quality, devs might care less about their own testing. I think that's the specific downside they're looking for, even if B sometimes happens in practice. Agree?
I think B, since limited communication is a pretty common issue when teams are separate.
C/D? I get why people pick C for project delays, but ISTQB focuses on developers losing ownership over quality when there’s independent testing, so D fits better. Pretty sure D is what they’re asking for but open to other views.
Its D, had something like this in a mock test and that's what it wanted.
Option B makes sense to me because if testers and devs aren't close, communication could drop, making bug fixing slower. I think that's a pretty big disadvantage of having separate teams. Maybe I'm missing something though.
Developers can lose a sense of responsibility for quality, so D. If they rely on independent testers to find issues, sometimes they don't focus as much on their own code quality. Pretty sure that's what ISTQB wants here. Agree?
Be respectful. No spam.
