ATDD is gaining speed and we need great tools to facilitate it. Writing tests first is a great way to design and ensure maintainability of code, but ATDD takes it a step further and brings our attention to the client's requirements. Pepino allows those client requirements to be turned into automated executable specifications that can be run over and over again.

1. ATDD con Pepino
Byron Sommardahl

2. Acceptance Criteria:
Formatted specification of
client desires or
requirements.
Given a manager
When I drink coffee
Then I get things done.

3. Test-Driven Development (TDD):
Designing and creating
production code by (first)
writing tests that prove
that something
accomplishes its goal.
Not just tests, but tests FIRST.

4. Unit Test:
Tests that cover a small,
isolated unit of code.
Isolated means no interference
from dependencies.

5. Integration Test:
Tests that cover
functionality across
multiple layers.
Many times, integration tests are
only useful for a while, then get
thrown away.

6. Integration Test:
Tests that cover
functionality across
multiple layers.
Many times, integration tests are
only useful for a while, then get
thrown away.

7. Acceptance Test:
Tests that confirm the
fulfillment of client’s
acceptance criteria.
Similar to integration tests, but
from the user’s perspective.

8. Metodos de Acceptance Test:
Human
Vs
Automation
You can never completely
replace human testers!

9. Automated Acceptance Testing:
… Meh
It’s soooooooooo hard!

10. Solutions Exist:
• Xamarin Test Cloud
• Sauce Labs
• Various Others
All expensive. None created
to facilitate ATDD.

11. Meet “Pepino”:
• Entire team can contribute
• Live reports on working
functionality
• Facilitates ATDD
• Side-by-side testing of web
user interfaces and http
APIS.

12. Meet “Pepino” (cont’d):
• Integration with CI server
• Made in Honduras
• Free (right now)

14. Get an invitation:
@pepinoApp
(Twitter)