I’m a little surprised you didn’t mention the Triple A acronym. Though I’m not sure if I’ve ever heard my teacher or any of the mentors say “Triple A.”
It stands for “Arrange, Act, Assert.”
For example: all new user records should be initialized with certain properties set to default values. First you arrange what you need to create a new user record. Then you act to create the new user record. And then you assert that the specified properties are indeed set to default values.
Of course that test would probably get split up into smaller tests, for the sake of granularity. They would then each show the AAA pattern.