Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

iSQI CTAL-TAE Exam - Topic 3 Question 35 Discussion

You have been asked to determine a TAS for a new release of a SUT, test should be automated wherever. The new release will consist of 5 new interfaces and an amendment to 3 existing interfaces. The new and amended interface will be deliver incrementally in 3 sprints, each lasting 2 weeks.What would be the BEST Test Automation Solution (TAS) design in this scenario?
A) Automate tests at both Component and System Level. Only do this automation once every interface has been fully developed or amended and manual testing has completed successfully. and C) Automate the tests at two levels, Component and System level. Create customized hooks at Component level for interface not yet developed or amended. Only use the newly developed or amended interfaces to test at System level.
B) Automate tests at one level only, System level. Use only the newly developed interfaces and do not create any customized interfaces/test hooks.
D) Automate a test at once level, component level, Create customized interface/test hooks for this level where the interface has not yet been developed or amended.

iSQI CTAL-TAE Exam - Topic 3 Question 35 Discussion

Actual exam question for iSQI's CTAL-TAE exam
Question #: 35
Topic #: 3
[All CTAL-TAE Questions]

You have been asked to determine a TAS for a new release of a SUT, test should be automated wherever. The new release will consist of 5 new interfaces and an amendment to 3 existing interfaces. The new and amended interface will be deliver incrementally in 3 sprints, each lasting 2 weeks.

What would be the BEST Test Automation Solution (TAS) design in this scenario?

Show Suggested Answer Hide Answer
Suggested Answer: A, C

Contribute your Thoughts:

0/2000 characters
Lindy
4 days ago
D could work too, but I feel like it limits testing scope.
upvoted 0 times
...
Loren
9 days ago
I'm surprised no one mentioned the risks of automating too early.
upvoted 0 times
...
Mauricio
14 days ago
Wait, why not just go with A? Seems safer to wait for full development.
upvoted 0 times
...
William
19 days ago
Totally agree, C covers both levels effectively!
upvoted 0 times
...
Alton
24 days ago
I think option C makes the most sense for thorough testing.
upvoted 0 times
...
Wenona
29 days ago
I’m a bit confused about whether we should focus on just the new interfaces or include the amended ones too. I feel like that could affect our choice.
upvoted 0 times
...
Lyndia
1 month ago
I’m leaning towards option C because it mentions creating customized hooks, which seems like a good way to handle interfaces that aren’t fully ready yet.
upvoted 0 times
...
Pa
1 month ago
I think we practiced a similar question where we had to choose between component and system level automation. I feel like automating at both levels could be beneficial, but it might be too much work.
upvoted 0 times
...
Gail
1 month ago
I remember we discussed the importance of early automation, but I'm not sure if we should wait for all interfaces to be fully developed before starting.
upvoted 0 times
...

Save Cancel