Test Maintainability

Question 1

In what sense, Automation Complexity is a dual-edged sword?

Answer 1

In one side, allows to build intelligence into our scripts so that they better simulate a
human tester running a test.
But in the other side, we need to handle an ever-increasing amount of complexity in the
SUT that we work on.

Question 2

In which sense we can move intelligence up to the TAA and/or TAF and out of the script?

Answer 2

by putting intelligence into callable functions rather than having to program intelligence into each script individually

Question 3

What is the benefit of make our scripts more scalable and maintainable?

Answer 3

If our code which adds intelligence fails, it will make a lot of scripts fail, but fixing them all can be done at a single point of contact.

Question 4

How can we achieve scalability and maintainability in our scripts?

Answer 4

By moving more intelligence upward and out of the scripts themselves

Question 5

other name for “aggregate functions”:

Answer 5

“wrapper functions”

Question 6

What kind of effort we should put into the failing block?

Answer 6

• The log statements should be comprehensive such to cut down the troubleshooting effort when a test fails.
• The cleanup functionality should ensure that the test suite can continue on to the next test.

Question 7

What do we need that a test tell us?

Answer 7

To tell us what we don’t already know about the SUT, its environment, and its usage

Question 8

Why it is so important to discuss the automation with the developers in your organization?

Answer 8

To prevent constant breakage of your automation that deals directly with the HTML.

Question 9

How can we make our code more readable?

Answer 9

Defining global names (variables, constants, function names, etc.)

Question 10

Easier code maintenance usually means

Answer 10

fewer regression defects when changes are made.

Question 11

Why are meaningful comments so important in our automation code?

Answer 11

Because we can forget from one day to another the clever thing we did to solve a problem and more people will start putting their fingers into our code.

Question 12

How can we achieve certainty when it comes to data used in our automation project?

Answer 12

By creating isolated test accounts and fixtures that are specifically to be used by automation scripts.

Question 13

What are the features of the test accounts and fixtures that we need to make available exclusively for automated testing?

Answer 13

• Enough different accounts that multiple tests should not interfere with each other’s data.
• With enough data in these accounts to make them simulate real accounts.
• If the SUT has different types of users (e.g., novices, techno geeks, power users, etc.) these should be modeled in our test accounts.

Question 14

What standards and guidelines should be adopted to deal with Logging files?

Answer 14

• Use consistent naming conventions and save the files to consistent folders.
• Consider making a folder with a timestamp in the name.
• If multiple machines are running the automation, or if testing in different environments, consider adding the workstation name or environment names to the folder names.
• Think of including time stamps in the file names.
• If the files are not needed in the future, put them into directories that can be destroyed without harm.
• If the files need to be saved, make sure that your folder structure includes that information.