Enable poke testing

Set up very basic test running so you can poke their system and see the result.

The Change

As soon as you have any part of an integration working, set up a basic test framework so that you can start writing poking tests.

The Value Proposition

The hardest part of an integration is its invisibility. We will need to try out many different things and record what happens. This is exactly the spec for a set of automated tests.

Creating a real, if simple, unit test framework for the integration boundary provides the following benefits:

  1. You don’t have to throw away the last experiment to run your next one.
  2. Quickly run all of your experiments at once.
  3. Easily communicate interactions — even unexpected ones — with the team.
  4. Create a starting point to use TDD as if You Mean It to grow your code.
Please log in

This content is only available to students. Please log in to access it.