MENU
You have implemented a keyword-driven scripting framework, which uses a test execution tool to run the tests. This has been in use for the past year and all of the teams now use this framework as the standard approach for test execution.
The teams all work on different aspects of the SUT and they have all experienced significant benefits in the use of this scripting framework. However, on closer examination, you have discovered that there are numerous instances where the teams have the same functionality to test but are using different keywords.
One of your objectives for improvement is to create consistency among the teams.
What is the BEST way to handle this situation?
Suggested Answer: D
Get Premium CT-TAE Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
20 comments · newest first
CR
Cristy
10 months ago
Option C could work, but it might not be enough for real consistency.
DA
Dante
11 months ago
Wait, they’ve been using different keywords for a year? That’s wild!
RE
Reita
11 months ago
I agree with D too! Consistency is key for collaboration.
PI
Pilar
11 months ago
But what if teams have unique needs? Not all keywords will fit.
KI
Kizzy
11 months ago
I think option D makes the most sense. Central library sounds efficient!
MA
Matilda
12 months ago
Creating a central library sounds like a solid plan. It could really help reduce confusion and redundancy among teams. I hope that's the right choice!
ED
Edwin
12 months ago
I practiced a similar question where we had to standardize testing processes. I think providing guidelines, like in option C, could help, but it might not be enough.
AV
Avery
12 months ago
I'm not entirely sure, but I think moving to a model-based approach could complicate things. I feel like we should stick to what we know for now.
MA
Malissa
1 year ago
I remember discussing the importance of consistency in keyword usage during our last study group. It seems like option D might be the best way to achieve that.
HI
Hillary
1 year ago
I'm feeling pretty confident about this one. I think the best approach would be to provide each team with a set of guidelines and naming conventions for the keywords. That way, they can still have some autonomy, but there's a clear standard in place.
KA
Karan
1 year ago
Hmm, this is an interesting problem. I think creating a central library of keywords and definitions could be a great way to standardize things across the teams. That way, they can still have some flexibility, but there's a common foundation to work from.
TA
Tawanna
1 year ago
I'm a bit confused by this question. It sounds like the teams are already seeing benefits from the scripting framework, so I'm not sure if "doing nothing" is really the best option. Maybe a combination of guidelines and a central library would be the way to go to maintain consistency.
MY
My
1 year ago
This seems like a tricky situation. I'm not sure if moving to a model-based approach is the best solution, as that could be a significant change for the teams. Providing guidelines and naming conventions might be a good starting point, but a central library of keywords could also help standardize things.
TH
Thurman
1 year ago
Hmm, the question mentions a control not created exception, so I'm guessing the issue is with the page navigation and the timing of when the controls are created. I'll need to think through the different options carefully.
AI
Aileen
1 year ago
This seems like a straightforward question about the purpose of an Issue Report. I think I've got a good handle on this concept, so I'll carefully read through the options and select the best answer.
DE
Derick
2 years ago
Or we could create a central library of keywords for everyone to use.
KI
Kirk
2 years ago
Well, maybe we can provide guidelines and naming conventions to help those teams.
LA
Latrice
2 years ago
But what about the teams who are happy with the way they are working currently?
DE
Derick
2 years ago
I agree with Kirk, having models with keywords will create consistency.
KI
Kirk
2 years ago
I think we should move to a model-based approach to scripting.