After thinking about guidelines and examining his code,
Dan decided to add a few slides to his presentation about project structure,
test names, and tags and makes a mental note to explain AAA to his team.
He does not try to create a test code in standard,
just a few pointers on how you can use the testing framework in a way
that will help him and his team write better tests and not provide
rules, but explain the motivation of each decision and how it makes
sense in the team's project.
As you've seen, you must keep your guidelines simple.
Do not try to create a long standard document.
By following a few rules, you can make a big difference.
Don't try to define every aspect of writing tests.
You can't.
You will only confuse your team.
Instead, give a few simple rules just to make sure that the
code base is consistent and every team member knows where
everything is and how to write new tests.