Is AAA good practice for coded interface tests?

Question

I use the AAA syntax (Arrange, Act, Assert) in all of my automated tests (unit tests, system tests, etc.). I recently started writing tests for the encoded interface. Now I am wondering if the AAA syntax is suitable here. Unlike unit tests, where each test has one act and claims (or more than one statement), and I can have hundreds of them that will work in less than a couple of minutes, tests with a coded interface will work much longer. Therefore, if I write coded user interface tests in the same way as I write my unit tests, they will need several hours (if not longer).

If I compare tests with a coded UI with manual UI tests, then in the mental tests do not use the AAA syntax to save time (without repeating the same “Arrange” action again to check the field value after another click).

What do you do in your applications? how do you recommend writing coded interface tests?

Answer 1

. . . . . AAA, .

. , . CodedUI , . , .

My CodedUI :

[TestMethod]
public void VerifyWhenThisThenThis() 
{
   // Prepare test data, Perform prerequisite action

   // Do test

   // One or more assertions to verify one major requirement only. 

   // If other major verification exist then split the test case 
   // and write a new test method for it.
}

, ( , ). , .