3\ What you start to notice is that everyone assumes the other knows what unit #testing is but it’s when you ask “What do the unit tests test?” Thats when you get some interesting responses.
4\ Everyone seems to have a different opinion on what makes a unit but also what makes a a good and bad unit tests 
5\ So why not (as a stop gap) just call them Code tests. I know what you might be thinking “That could mean anything! 😳" But that’s the point…
6\ Calling them Code #tests also gets the team to ask the same thing which then gives you the opportunity to start that discussion. But what do you actually talk about? 🤔
7\ Now you can ask them “What does a unit mean to you?” & “What characteristics do good and bad tests have”? Get them to put it on post it notes
8\ Then you can go about putting the responses into groups and themes to build a team understanding of what a unit tests is and what makes a good and bad code test
9\ Its also a really good opportunity to improve their understanding of what is a unit is and what about them makes it a good and bad tests
10\ Now you’ve got a hight level team understanding you want to make that a little more concrete. Something that brings alignment with the team, allows dev autonomy in writing them but also makes them accountable to actually do the work
11\ You could just stick with code but we’ve seen where that has got us (see above). So we need something lightweight but what?
12\ Well here is one example (not a unit test) but something that has all the elements of what we’re looking for
13\ Notice how short and to the point it is, keeping the language very simple and easy for everyone to understand including developers or otherwise 🤔
14\ So how would this work for code #tests?
15\ How does this build alignment? By giving the team a common language and making their decision on what a unit is accessible
16\ How does this build autonomy? By only explaining the what of good and bad tests with example for the teams actual code base
17\ how does this build accountability? Because now no one can say I didn’t know what a unit was or what makes a bad or good test. But also gives them a reference point to find out more from the team. Which would hopefully kick off the discussion again for new starts
18\ The most important parts are the discussion with the team but also encoding that discussion in someway that they can references again when someone like me shows up asking: What do the unit tests do?
