iSQI Exam CTAL-TM_Syll2012 Topic 1 Question 22 Discussion

Actual exam question for iSQI's CTAL-TM_Syll2012 exam

Question #: 22
Topic #: 1

[All CTAL-TM_Syll2012 Questions]

In the next two months some new features will be constantly added to new releases of a project you are working on as Test Manager.

You have identified as one of the main project risks, that the requirements specification will still be incomplete when your team starts the test design and implementation phase.

Some requirements will most likely be completed too late to allow a proper test preparation. You and your test team have already worked on several similar past projects in the same organization.

Which one of the following options would you expect to be the most effective at mitigating this risk?

K4 3 credits

ADon't prepare any test and just run the regression test suite to check that the new features don't introduce regression

BMake reasonable assumptions about the missing details and design lightweight tests that can be easily updated during test execution

CDon't design any test until the test execution starts, then communicate that test execution is blocked due to incomplete requirements

DEven if there are only few details missing, escalate the risk to the project manager without preparing any tests

Show Suggested Answer

Suggested Answer: C

by Viva at May 05, 2022, 07:35 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel

Elvera

3 months ago

Escalating the risk without preparing any tests? That's like trying to fight a fire with a squirt gun. Option B is the only sensible choice here, folks.

upvoted 0 times

Holley

1 months ago

I think we should go with Option B and adapt our tests as needed. It's better to be prepared than to wait around for everything to be perfect.

upvoted 0 times

...

Son

1 months ago

Exactly, we can't afford to wait until the last minute to start testing. Option B is the most practical approach in this situation.

upvoted 0 times

...

Merissa

2 months ago

I agree, we need to be proactive and start designing lightweight tests that can be easily updated as more details come in.

upvoted 0 times

...

Stephania

2 months ago

Option B is definitely the way to go. We can't just sit around and wait for all the requirements to be perfect before starting testing.

upvoted 0 times

...

Merrilee

3 months ago

Haha, Option A is a joke, right? Just running the regression suite? That's like trying to put a Band-Aid on a broken leg. Option B is definitely the way to go.

upvoted 0 times

Terrilyn

1 months ago

Haha, yeah, Option A would be a disaster. Option B is definitely the best approach to handle incomplete requirements.

upvoted 0 times

...

Ines

2 months ago

I agree, Option B is the most effective at mitigating the risk of incomplete requirements. Lightweight tests that can be easily updated during test execution are key.

upvoted 0 times

...

Youlanda

2 months ago

Option A is definitely not the way to go. It's important to design tests based on reasonable assumptions about missing details.

upvoted 0 times

...

Ernest

3 months ago

Option C is just asking for trouble. Communicating that test execution is blocked is not going to solve anything. We need to be proactive and work with what we have.

upvoted 0 times

Micah

1 months ago

Escalating the risk without even trying to work with what we have doesn't seem like a good idea. Option B is definitely the way to go.

upvoted 0 times

...

Frank

1 months ago

Definitely, waiting until test execution starts to communicate issues will only cause delays. Option B seems like the best way to mitigate the risk.

upvoted 0 times

...

Gabriele

1 months ago

I agree, being proactive and making reasonable assumptions will help us stay on track with testing.

upvoted 0 times

...

Aleisha

1 months ago

Option B sounds like the most practical approach. We can design lightweight tests that can be easily updated as more details become available.

upvoted 0 times

...

Moon

1 months ago

Let's go with Option B and adapt our tests as needed. It's better to be prepared than to wait for complete requirements.

upvoted 0 times

...

Holley

1 months ago

Definitely, waiting until test execution to communicate issues will only cause delays. Option B is the way to go.

upvoted 0 times

...

Casie

2 months ago

I agree, being proactive and making reasonable assumptions will help us stay on track with testing.

upvoted 0 times

...

Luisa

2 months ago

Definitely, waiting until test execution to communicate issues will only cause delays. Option B is the way to go.

upvoted 0 times

...

Richelle

2 months ago

Option B sounds like the best approach. We can design lightweight tests that can be easily updated as more details become available.

upvoted 0 times

...

Kassandra

2 months ago

I agree, being proactive and making reasonable assumptions will help us stay on track with testing.

upvoted 0 times

...

Cheryll

2 months ago

Option B seems like the most practical approach. We can design lightweight tests that can be easily updated as more details come in.

upvoted 0 times

...

Bonita

3 months ago

I agree with Becky. Option B is the best choice here. We can't afford to not prepare any tests or wait until the last minute. Making assumptions and designing flexible tests is the way to go.

upvoted 0 times

...

Option B seems like the most reasonable approach. Designing lightweight tests that can be easily updated is better than not testing at all or delaying the process. We've dealt with incomplete requirements before, so this approach should work.

upvoted 0 times