iSQI CTFL-AT Exam - Topic 3 Question 47 Discussion

Actual exam question for iSQI's CTFL-AT exam

Question #: 47
Topic #: 3

You are working on an Agile project and have been asked to implement exploratory testing for the current sprint. Which one of the following is a correct approach to adopt?

AAllocate independent testers to design exploratory tests using test charters in time boxed sessions. Plan to run all sessions in parallel with each session lasting more than 5hours.

BAsk experienced testers to try and find new defects by using the system without the constraint of documentation and tools.

CUse testers who have not been involved in the sprint to write new test cases from the user stories. These test cases are then executed in a time boxed session for the sprint.

DAsk experienced testers to prepare test charters for time boxed sessions lasting no more than 2hours. Tests should be designed and executed within each session using heuristics, creativity and intuition.

Show Suggested Answer

Suggested Answer: B

by Orville at Mar 09, 2025, 08:32 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Ming

3 months ago

I like D, but I wonder if the time limit might rush the testers.

upvoted 0 times

...

Kayleigh

3 months ago

Option B sounds good too, but no constraints can lead to chaos.

upvoted 0 times

...

Sabina

3 months ago

Wait, 2 hours? That seems too short for thorough testing.

upvoted 0 times

...

Justine

4 months ago

Totally agree, 2-hour sessions keep it focused!

upvoted 0 times

...

Effie

4 months ago

I think option D is the best approach for exploratory testing.

upvoted 0 times

...

Laticia

4 months ago

I recall that exploratory testing should be flexible, but I’m not sure if option A's long sessions are effective. It seems like they could lead to tester fatigue.

upvoted 0 times

...

Tamesha

4 months ago

I practiced a similar question, and I think time-boxed sessions are important for keeping focus. Option D sounds familiar, but I’m not confident about the 2-hour limit.

upvoted 0 times

...

Dominque

4 months ago

I'm not entirely sure, but I feel like asking experienced testers to just explore without constraints, like in option B, could lead to some interesting findings.

upvoted 0 times

...

Irene

5 months ago

I remember we discussed exploratory testing in class, and I think it involves using creativity and intuition, so maybe option D is the right choice?

upvoted 0 times

...

Reed

5 months ago

Option B sounds good to me - just letting the testers explore the system freely without constraints. But I'm not sure if that's the "correct" approach the question is looking for.

upvoted 0 times

...

Ollie

5 months ago

I think option D is the best choice here. The key is using experienced testers, time-boxed sessions, and heuristics to discover new issues, rather than just executing pre-written test cases.

upvoted 0 times

...

Angelica

5 months ago

Hmm, I'm a bit confused. Exploratory testing is supposed to be unscripted, but option A mentions designing tests in advance. I'm not sure which approach is correct.

upvoted 0 times

...

Gertude

5 months ago

This question seems straightforward - the correct approach is option D, where experienced testers use test charters and time-boxed sessions to explore the system creatively.

upvoted 0 times

...

Reita

10 months ago

I'm just going to throw the entire user manual out the window and see what happens. That's the true spirit of exploratory testing, right?

upvoted 0 times

Gilberto

9 months ago

D) Ask experienced testers to prepare test charters for time boxed sessions lasting no more than 2hours. Tests should be designed and executed within each session using heuristics, creativity and intuition.

upvoted 0 times

...

Cary

10 months ago

B) Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools.

upvoted 0 times

...

Adela

10 months ago

Option C looks like it's trying to shoehorn in some traditional test case writing into an exploratory testing approach. That's not quite the right way to go about it.

upvoted 0 times

...

Rodolfo

10 months ago

I'm going with option D as well. The key is to have experienced testers design and execute the tests within the time-boxed sessions, using their heuristics and intuition.

upvoted 0 times

...

Yuette

10 months ago

Option A sounds like a bit of an overkill. Allocating independent testers and running sessions longer than 5 hours doesn't really align with the principles of exploratory testing.

upvoted 0 times

Ronald

9 months ago

D) Ask experienced testers to prepare test charters for time boxed sessions lasting no more than 2 hours. Tests should be designed and executed within each session using heuristics, creativity and intuition.

upvoted 0 times

...

Della

9 months ago

C) Use testers who have not been involved in the sprint to write new test cases from the user stories. These test cases are then executed in a time boxed session for the sprint.

upvoted 0 times

...

Michal

10 months ago

B) Ask experienced testers to try and find new defects by using the system without the constraint of documentation and tools.

upvoted 0 times

...

Blondell

11 months ago

I think option D is the correct approach. Exploratory testing should be done in short, focused sessions where testers can use their creativity and intuition to find defects without being constrained by documentation or tools.

upvoted 0 times