Revisions.

Author: Jason Carter

acceptance_specs.md

@@ -33,7 +33,7 @@
 
 ---
 
-## ...so that means, write a unit test, implement it
+## ...so that means, write a __unit__ test, implement it
 ![fit right](http://www.memes.at/faces/questioning.jpg)
 
 ---
@@ -42,6 +42,10 @@
 
 ---
 
+## On __unit__ tests...
+
+---
+
 ## But there was a problem...
 
 ---
@@ -50,14 +54,18 @@
 
 ---
 
-## So I got better at writing integration tests...
+## So I got better at writing __integration__ tests...
 
 ---
 
 ## __Integration tests__ gave me confidence that __my classes worked together__ as I expected
 
 ---
 
+## On __integration__ tests...
+
+---
+
 ![fit](https://i0.wp.com/motionmill.com/wp-content/uploads/2013/03/what-the-customer-really-wanted-528x514.gif)
 
 ---
@@ -123,32 +131,36 @@
 
 ---
 
-## Isn't that what QA is for?
+## Isn't that what __QA__ is for?
 ![fit left](http://www.memes.at/faces/questioning.jpg)
 
 ---
 
-## QA has better things to do
+## They have __better__ things to do
 
 ---
 
-## They're great at finding edge cases
+## They're great at finding __edge cases__
 ![fit left](https://pbs.twimg.com/media/CFBzC9gWgAAXrZL.jpg)
 
 ---
 
-## The __acceptance test__ tells you when you're __done__... immediately
+## They're great at identifying __wonky__ behavior
 
 ---
 
-## We're starting to pair with QA on these tests
+## They should be your __last__ line of defense, __not your first__
 
 ---
 
 ![fit](http://www.kappit.com/img/pics/201601_0639_igdgf_sm.jpg)
 
 ---
 
+## The __acceptance test__ tells you when you're __done__... immediately
+
+---
+
 ## Pattern becomes:
 - Write the __acceptance test__ to know when the feature is done
 - Test drive the implementation with __unit__ and __integration specs__
@@ -245,7 +257,15 @@
 
 ---
 
-## Not scoping
+## Not scoping your finders
+
+---
+
+## Asynchronous code
+
+---
+
+## Mixing setup and actions
 
 ---
 
@@ -651,7 +671,7 @@ end
 
 ---
 
-## How do I start doing this?
+## How do I start?
 
 ---