WEBVTT

00:00:01.140 --> 00:00:04.510
After thinking about guidelines and examining his code,

00:00:04.580 --> 00:00:08.750
Dan decided to add a few slides to his presentation about project structure,

00:00:08.760 --> 00:00:14.540
test names, and tags and makes a mental note to explain AAA to his team.

00:00:14.550 --> 00:00:17.520
He does not try to create a test code in standard,

00:00:17.520 --> 00:00:22.680
just a few pointers on how you can use the testing framework in a way

00:00:22.680 --> 00:00:26.710
that will help him and his team write better tests and not provide

00:00:26.710 --> 00:00:30.760
rules, but explain the motivation of each decision and how it makes

00:00:30.760 --> 00:00:32.729
sense in the team's project.

00:00:32.840 --> 00:00:36.410
As you've seen, you must keep your guidelines simple.

00:00:36.420 --> 00:00:39.070
Do not try to create a long standard document.

00:00:39.160 --> 00:00:42.560
By following a few rules, you can make a big difference.

00:00:42.840 --> 00:00:46.170
Don't try to define every aspect of writing tests.

00:00:46.140 --> 00:00:46.940
You can't.

00:00:47.040 --> 00:00:48.860
You will only confuse your team.

00:00:49.140 --> 00:00:52.870
Instead, give a few simple rules just to make sure that the

00:00:52.870 --> 00:00:56.540
code base is consistent and every team member knows where

00:00:56.540 --> 00:00:59.370
everything is and how to write new tests.