Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25

- Free Preparation Discussions

ISTQB Exam ISTQB-CTFL Topic 2 Question 23 Discussion

Actual exam question for ISTQB's ISTQB-CTFL exam

Question #: 23
Topic #: 2

[All ISTQB-CTFL Questions]

You are an experienced tester on a project with incomplete requirements and under pressure to deploy.

What type of testing should you do?

ADecision-based testing.

BChecklist-based testing.

CError guessing.

DExploratory testing.

Show Suggested Answer

Suggested Answer: D

Component integration tests are designed to verify the interactions and interfaces between integrated components. These tests should be carried out after component testing (where individual components are tested in isolation) but before system testing (where the entire system is tested as a whole). This ensures that any issues arising from the integration of components are identified and resolved early in the testing process, making option D the correct answer.

by Eugene at Jun 20, 2024, 12:09 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Jamie

2 months ago

D) Exploratory testing. Incomplete requirements? Sounds like a job for Captain Improvisation!

upvoted 0 times

...

Miesha

2 months ago

A) Decision-based testing. I'll just flip a coin and hope for the best. What could go wrong?

upvoted 0 times

Lashaunda

19 days ago

C) Error guessing. Let's try to anticipate where errors might occur and test those areas.

upvoted 0 times

...

Kimberely

20 days ago

D) Exploratory testing. We should explore the system and find any unexpected issues.

upvoted 0 times

...

Maira

21 days ago

B) Checklist-based testing. We need to make sure we cover all possible scenarios.

upvoted 0 times

...

...

Marti

3 months ago

C) Error guessing. Incomplete requirements? Time to channel my inner Sherlock Holmes and predict all the things that could go wrong!

upvoted 0 times

Rolland

29 days ago

D) Exploratory testing.

upvoted 0 times

...

Leontine

1 months ago

B) Checklist-based testing.

upvoted 0 times

...

Lavera

1 months ago

D) Exploratory testing.

upvoted 0 times

...

Leontine

2 months ago

C) Error guessing.

upvoted 0 times

...

Glory

2 months ago

B) Checklist-based testing.

upvoted 0 times

...

Leah

2 months ago

A) Decision-based testing.

upvoted 0 times

...

Arleen

2 months ago

A) Decision-based testing.

upvoted 0 times

...

...

Margurite

3 months ago

B) Checklist-based testing. Gotta cover all the bases, even if the requirements are sketchy.

upvoted 0 times

Vallie

1 months ago

C) Error guessing.

upvoted 0 times

...

Antione

1 months ago

B) Checklist-based testing.

upvoted 0 times

...

Keith

2 months ago

D) Exploratory testing.

upvoted 0 times

...

Andra

2 months ago

A) Decision-based testing.

upvoted 0 times

...

...

Jesusa

3 months ago

D) Exploratory testing. With incomplete requirements, I need a flexible approach to uncover issues quickly.

upvoted 0 times

Marcos

2 months ago

A) Decision-based testing might not be as effective with incomplete requirements.

upvoted 0 times

...

Charlette

2 months ago

D) Exploratory testing is definitely the way to go in this situation.

upvoted 0 times

...

...

Melynda

3 months ago

But what about error guessing? It could help us uncover unexpected issues.

upvoted 0 times

...

Evangelina

3 months ago

I agree, exploratory testing allows us to adapt to the changing requirements.

upvoted 0 times

...

Paris

3 months ago

I think we should do exploratory testing.

upvoted 0 times

...