MENU
You have been asked to automate a set of functional tests at system Test level via the CLI of the SUT for the first release of a software system. The automated tests will be delivered to the learn in change of maintenance testing, who will use them for part of the regression testing. They have the following requirements.
1. The automated tests must be as fast and cheap to maintain as possible
2. The cost of adding new automated tests must be as low as possible
3. The automated tests must have a high level of independence from the tool itself
Which of the following scripting techniques would be MOST suitable?
Suggested Answer: C
Get Premium CT-TAE Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
38 comments · newest first
MI
Mitsue
10 months ago
Structure scripting could work, but it’s not as common.
TY
Tyra
11 months ago
Really? I’m not sure data-driven is the best fit here.
SH
Shelton
11 months ago
Linear scripting? Nah, too rigid for this.
GA
Gaston
11 months ago
I think keyword-driven might be better for independence.
ER
Erinn
11 months ago
Data-driven scripting is the way to go!
MA
Marlon
12 months ago
Structure scripting sounds familiar, but I can't recall if it really meets the independence requirement as well as the others.
JO
Josphine
12 months ago
I remember practicing with linear scripting, but it seems like it wouldn't be flexible enough for this scenario.
MA
Markus
12 months ago
I'm not entirely sure, but keyword-driven scripting could also fit the requirements since it promotes reusability and independence from the tool.
TR
Truman
1 year ago
I think data-driven scripting might be a good choice since it allows for easy updates and can handle multiple test cases with minimal changes.
AL
Alberta
1 year ago
I'm a bit confused by the differences between the scripting techniques. Can someone explain the pros and cons of each one in the context of this question? I want to make sure I understand before I commit to an answer.
AN
An
1 year ago
Keyword-driven scripting sounds like the way to go. It should give us the flexibility to add new tests easily and keep the maintenance costs low. I feel pretty confident about this one.
CA
Carey
1 year ago
Linear scripting seems too simplistic for this scenario. We need something more robust and maintainable. I'm leaning towards keyword-driven, but I'll double-check the requirements to be sure.
JU
Junita
1 year ago
Hmm, I'm not sure. Data-driven scripting could also work well, as it would allow us to easily add new tests without modifying the core script. I'll have to think this through a bit more.
RO
Royal
1 year ago
This looks like a classic test automation question. I think keyword-driven scripting would be the best approach here. It should meet the requirements of being fast, cheap to maintain, and independent of the tool.
HE
Herminia
1 year ago
This seems pretty straightforward. I think Journey Builder and Engagement Split would be the way to go to track the subscriber's engagement and send further messages based on that.
HO
Hoa
1 year ago
I've got a good feeling about this one. Option D looks right to me - multicast traffic is transported in the overlay and the EID space, not the underlay. The other options don't seem to fit the SD-Access architecture as well.
GL
Glenna
1 year ago
Ah, this is an easy one. ProcessExplorer is the tool that keeps a backup of deleted items, so I'm going with that.
TR
Trina
1 year ago
Keyword-driven scripting is the perfect choice. It's like a secret language that only the test engineers can understand. Shh, don't tell the maintenance team!
MA
Markus
1 year ago
C) Linear scripting
CE
Cecil
1 year ago
B) Keyword-driven scripting
RE
Rex
1 year ago
A) Data-driven scripting
RU
Ruthann
1 year ago
Keyword-driven scripting is the way to go! It's like building a LEGO set - you just need to follow the instructions.
HE
Herminia
1 year ago
C) Linear scripting
GE
Geoffrey
1 year ago
B) Keyword-driven scripting
GO
Goldie
1 year ago
A) Data-driven scripting
TA
Tamie
1 year ago
I'll have to go with keyword-driven scripting. It's like writing a script in plain English, which should make it easy for the maintenance team to understand and update.
MA
Mary
1 year ago
User 4: Data-driven scripting might be too complex and costly to maintain in this case.
MA
Mari
1 year ago
User 3: Plus, it will help in keeping the automated tests independent from the tool itself.
YO
Yolando
1 year ago
User 2: Definitely, it will make it easier for the maintenance team to understand and update the tests.
RO
Ronny
1 year ago
User 1: I agree, keyword-driven scripting sounds like the best option for this scenario.
RY
Ryan
1 year ago
Data-driven scripting seems like a good option too. It can help reduce the cost of adding new tests and make the tests more reusable.
TH
Thora
1 year ago
I disagree, I think data-driven scripting would be better for independence from the tool itself.
EI
Eileen
1 year ago
I agree with Kiley, keyword-driven scripting allows for easy maintenance and low cost of adding new tests.
KI
Kiley
2 years ago
I think keyword-driven scripting would be most suitable.
RO
Rosendo
2 years ago
I think keyword-driven scripting would be the most suitable approach. It aligns well with the requirements of easy maintenance and independence from the automation tool.
MY
Myong
1 year ago
C) Linear scripting
JO
Jolanda
1 year ago
B) Keyword-driven scripting
WI
William
1 year ago
A) Data-driven scripting