MENU
You are working on a project to develop an application that allows users to collaborate via bespoke, online whiteboards. The first release, delivering core functionality, highlighted misunderstandings of the user stories between testers, developers and the product owner during sprint development Since that release, the developers have agreed to implement a TDD approach for future software development.
Creation of the product backlog for the second release is underway and you have recommended to the project stakeholders that an atdd approach be adopted for the backlog's user stories. What would be a GOOD REASON for making this recommendation?
SELECT ONE OPTION
Suggested Answer: A
Get Premium CTAL-ATT Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
36 comments · newest first
TE
Tequila
11 months ago
Not sure if ATDD will solve all the issues we had.
KE
Keneth
11 months ago
D makes total sense after the last release.
GL
Gladys
12 months ago
Surprised that TDD needs ATDD to work well!
DA
Daniel
12 months ago
I think B is the better choice here.
FL
Flo
12 months ago
ATDD can really clear up misunderstandings!
EL
Elin
1 year ago
I feel like the test strategy mentioning automation is important, but it doesn't seem to directly relate to the misunderstandings we faced.
EM
Emeline
1 year ago
I vaguely recall that TDD and ATDD are related, but I can't remember if one is dependent on the other.
KA
Kasandra
1 year ago
I think option D makes sense because it directly addresses the misunderstandings we had in the first release.
LA
Lasandra
1 year ago
I remember discussing how ATDD can clarify requirements, but I'm not sure if it's the best reason for this situation.
FA
Fausto
1 year ago
Okay, let's break this down step-by-step. We have 3 QlikView developers, 2 business analysts accessing 5 documents, and 1 supervisor accessing 1 document. I think I know the right combination of CALs to cover this.
GA
Gabriele
1 year ago
This is a tough one, but I'm feeling pretty confident I can tackle it. I'll start by gathering all the stakeholder perspectives and see if we can find a compromise solution that works for everyone.
WA
Wava
1 year ago
Hmm, I'm a bit unsure about this one. The question mentions "identical stages and fields" for the new product cases, but additional stages and fields for the maintenance cases. I'll need to think carefully about which Salesforce features can handle that kind of mixed requirement.
DE
Delsie
1 year ago
I agree with Rebbeca. The key here is addressing those misunderstandings, and ATDD examples seem like the way to go. Plus, it's just good practice in general.
EL
Elin
1 year ago
B) The test strategy states that automation shall be used to minimize effort for execution of acceptance tests
CH
Cheryl
1 year ago
D) use of attd examples will help address the misunderstandings encountered in release 1
JO
Johanna
1 year ago
A) The team wants to start using BDD and therefore atdd must also be used
KE
Kenny
1 year ago
Haha, option A is just silly. BDD and ATDD are totally different things. You can do one without the other for sure.
AU
Audrie
1 year ago
I'm not so sure about that. I mean, TDD and ATDD are separate practices, right? I don't think they're necessarily linked in the way option C suggests.
JU
Justa
1 year ago
D) use of attd examples will help address the misunderstandings encountered in release 1
ST
Stephaine
1 year ago
B) The test strategy states that automation shall be used to minimize effort for execution of acceptance tests
JO
Joanne
1 year ago
A) The team wants to start using BDD and therefore atdd must also be used
RE
Rebbeca
1 year ago
Hmm, I think option D is the best choice here. Using ATDD examples can really help clarify the user stories and prevent those misunderstandings we saw in the first release.
FR
Frank
1 year ago
Absolutely, it will save us a lot of time and effort in the long run.
TU
Tula
1 year ago
It's important to have that clarity from the start to avoid any confusion later on.
NI
Nicolette
1 year ago
I agree, using ATDD examples will make sure everyone is on the same page with the user stories.
LI
Lisbeth
1 year ago
Option D is definitely the way to go. We need to address those misunderstandings from the first release.
PA
Paulina
1 year ago
Absolutely, it will save us a lot of time and effort in the long run.
OM
Omega
1 year ago
It's important to have that clarity from the start to avoid any confusion later on.
AN
Annmarie
1 year ago
I agree, using ATDD examples will make sure everyone is on the same page with the user stories.
RU
Ruthann
1 year ago
Option D is definitely the way to go. We need to address those misunderstandings from the first release.
LA
Lamar
1 year ago
Absolutely, option D is the way to go. It will ensure that the user stories are well-defined and understood by all team members.
CA
Cassandra
1 year ago
Yeah, I think using ATDD examples will provide a clear understanding for everyone involved in the project. It's important to avoid those misunderstandings.
BL
Blondell
1 year ago
I agree, option D seems like the most logical choice. It would definitely help address the misunderstandings we faced in the first release.
AM
Amie
2 years ago
I'm not sure about option D. Maybe we should consider option B for automation.
CU
Curtis
2 years ago
I agree with Truman. Using ATDD examples can definitely help address misunderstandings.
TR
Truman
2 years ago
I think option D is a good reason for recommending ATDD.