ATDD with Pepino

14
ATDD con Pepino Byron Sommardahl

Transcript of ATDD with Pepino

Page 1: ATDD with Pepino

ATDD con PepinoByron Sommardahl

Page 2: ATDD with Pepino

Acceptance Criteria:

Formatted specification of client desires or requirements.

Given a managerWhen I drink coffeeThen I get things done.

Page 3: ATDD with Pepino

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.

Page 4: ATDD with Pepino

Unit Test:

Tests that cover a small, isolated unit of code.

Isolated means no interference from dependencies.

Page 5: ATDD with Pepino

Integration Test:

Tests that cover functionality across multiple layers.

Many times, integration tests are only useful for a while, then get thrown away.

Page 6: ATDD with Pepino

Integration Test:

Tests that cover functionality across multiple layers.

Many times, integration tests are only useful for a while, then get thrown away.

Page 7: ATDD with Pepino

Acceptance Test:

Tests that confirm the fulfillment of client’s acceptance criteria.

Similar to integration tests, but from the user’s perspective.

Page 8: ATDD with Pepino

Metodos de Acceptance Test:

HumanVs

Automation

You can never completely replace human testers!

Page 9: ATDD with Pepino

Automated Acceptance Testing:

… Meh

It’s soooooooooo hard!

Page 10: ATDD with Pepino

Solutions Exist:

• Xamarin Test Cloud• Sauce Labs• Various Others

All expensive. None created to facilitate ATDD.

Page 11: ATDD with Pepino

Meet “Pepino”:

• Entire team can contribute• Live reports on working

functionality• Facilitates ATDD• Side-by-side testing of web

user interfaces and http APIS.

Page 12: ATDD with Pepino

Meet “Pepino” (cont’d):

• Integration with CI server• Made in Honduras• Free (right now)

Page 13: ATDD with Pepino
Page 14: ATDD with Pepino

@pepinoApp

Get an invitation:

(Twitter)