MENU
Consider A TAS for testing a desktop application via its GUI. All the test cases of the automated test suite contain the same identical sequences of steps at the beginning (to create the necessary objects when doing a preliminary configuration of the test environment and at the end (to remove everything created --specifically for the test itself during the preliminary configuration of the test environment). All automated test cases use the same set of assertion functions from a shared library, for verifying the values in the GUI fields ( e.g text boxes).
What is the BEST recommendation for improving the TAS?
Suggested Answer: B
Get Premium CT-TAE Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
SY
Sylvie
11 months ago
Wait, are we really doing all that setup and teardown manually?
LE
Lenny
11 months ago
C sounds good, but do we really need standard methods for everything?
HA
Hannah
12 months ago
A is interesting, but not sure if it's the best option.
KI
Kimbery
12 months ago
I think B could really help with overall testability!
ME
Merilyn
12 months ago
D seems like a solid choice for better organization.
JE
Jennie
1 year ago
I think improving the architecture could be beneficial, but it seems more like a long-term solution. I’m leaning towards D for immediate improvements.
YO
Youlanda
1 year ago
I feel like we practiced a similar question where standardization was key. Option C sounds familiar, but I wonder if it’s the best choice here.
BE
Belen
1 year ago
I'm not entirely sure, but I think implementing keywords with higher granularity might help too. It could make the tests more readable, right?
AL
Alaine
1 year ago
I remember discussing the importance of setup and teardown functions in our last class. It seems like option D could really streamline the test cases.
AL
Alpha
1 year ago
I'm a bit confused by this question. I know we need to create visuals from Kusto queries, but I'm not sure if Plotly is the best choice. TensorFlow is a powerful machine learning library, so maybe that could be used to analyze the data and generate visualizations? I'll have to do some more research on the different options.
TI
Tina
1 year ago
I think I've read that you might need to run it as root to see all the open files, but I'm not completely sure.
JI
Jina
1 year ago
Ah, I remember this from my Attachmate training. The mnemonic keyword for the Enter key is {enter}. Easy peasy!
HO
Hoa
1 year ago
Hmm, I'm a little unsure about this one. I'm torn between A and B. Offering free yarn could be a good incentive, but getting the active members to post more might be more effective in the long run. I'll have to think this through a bit more.
TA
Tasia
1 year ago
Option C could also be a good choice, but I think implementing standard setup and teardown functions is the more elegant solution here. It'll keep the test cases focused on the actual functionality being tested.
PA
Paris
1 year ago
Option C could also be a good choice, but I think implementing standard setup and teardown functions is the more elegant solution here. It'll keep the test cases focused on the actual functionality being tested.
PA
Paul
1 year ago
D) Implementing standard setup and teardown functions at test case level
AN
Angella
1 year ago
A) Implementing keywords with higher level of granularity
KA
Katie
1 year ago
Haha, talk about repetitive code! Sounds like they need to hire a good refactoring consultant to whip this test suite into shape. Option D is definitely the way to go.
DE
Denae
1 year ago
Haha, talk about repetitive code! Sounds like they need to hire a good refactoring consultant to whip this test suite into shape. Option D is definitely the way to go.
MI
Mitsue
1 year ago
D) Implementing standard setup and teardown functions at test case level
LO
Lorrie
1 year ago
C) Adopting a set of standard verification methods for use by all automated tests
LU
Lucina
1 year ago
B) Improving the architecture of the application in order to improve its testability
QU
Quinn
1 year ago
A) Implementing keywords with higher level of granularity
SH
Sharen
2 years ago
I agree with Staci. Having that common setup and teardown process in a shared function will make the test suite much more maintainable and easier to update in the future.
SI
Simona
1 year ago
D) Implementing standard setup and teardown functions at test case level
DI
Dierdre
1 year ago
A) Implementing keywords with higher level of granularity
VE
Verlene
2 years ago
I personally think adopting a set of standard verification methods for use by all automated tests would be more beneficial in the long run.
ST
Staci
2 years ago
Option D seems like the obvious choice here. Implementing standard setup and teardown functions at the test case level will help eliminate all that redundant code we're seeing in the beginning and end of each test case.
NA
Natalya
1 year ago
D) Implementing standard setup and teardown functions at test case level
CL
Clarence
1 year ago
C) Adopting a set of standard verification methods for use by all automated tests
SL
Slyvia
1 year ago
B) Improving the architecture of the application in order to improve its testability
CR
Cristal
1 year ago
A) Implementing keywords with higher level of granularity
RO
Rossana
2 years ago
I agree with Oliva. It would make the test cases more modular and easier to maintain.
OL
Oliva
2 years ago
I think implementing keywords with higher level of granularity would be the best recommendation.