The document discusses different types of software testing including acceptance testing, scenario based testing, user stories, acceptance criteria, functional testing, and unit testing. It explains that testing improves reliability, increases coverage, and combats technical debt while boosting team morale. Unit testing is the fastest but hardest to write while acceptance testing is the easiest to write but slowest and hardest to debug. User stories follow the format of "As a <user> I want <goal> so that <benefit>" and acceptance criteria use "Given <condition>, when <action>, then <result>" format.

1. Testing Made Easy
Micah Wood
@wpscholar
http://wpscholar.com/wctpa2015/

2. Why Test?

3. Long-Term Savings

4. Improve Reliability

5. Increase Coverage

6. Do The Impossible

7. Combat Technical Debt

8. Team Morale

9. Functional
Unit
Acceptance

10. Acceptance Testing
Scenario Based

11. Easiest to Write

12. Hardest to Debug

13. Slowest

14. Codeception

15. User Story

16. User Story
As a <who>
I want to <what>
So that <why>

17. User Story
As an Account Holder
I want to withdraw cash from an ATM
So that I can get money when the bank is closed

19. Acceptance Criteria

20. Acceptance Criteria
Given <condition>
When <action>
Then <result>

21. Acceptance Criteria
Given a user has an account
When they login
Then they should see a “Welcome <name>!” message

23. Functional Testing
Feature Based

24. Harder to Write

25. Easier to Debug

26. Faster

27. Unit Testing
Function Based

28. “Testing code isn’t hard. Writing testable code is.”

29. Hardest to Write

30. Easiest to Debug

31. Fastest

35. Questions?
Micah Wood
@wpscholar
http://wpscholar.com/wctpa2015/