Baton Manual

Chapter 12

Running a collection

A collection can be run end to end: every request in tree order, with its scripts and tests, in one pass. It is reached from the collection’s menu or from the command palette.

Eight requests, two of which failed — and the reason is in the row. — 1: A step that failed, with the reason in place; 2: A step that passed: tests, status, time; 3: Repeat the whole run
  1. A step that failed, with the reason in place
  2. A step that passed: tests, status, time
  3. Repeat the whole run
Figure 35: Eight requests, two of which failed — and the reason is in the row.

The heading counts the whole run: how many requests, how many failed, and the total tests passed. 1 is a step that failed, with the reason in place rather than hidden behind a click. 2 is one that passed, showing its tests, status and timing. 3 runs the lot again.

12.1Reading a failure

The two failures above are worth keeping, because they are the two kinds you will meet:

Row saysMeans
ResolveError: unresolved secrets: apiTokenThe secret has no value on this machine. Nothing was sent. Set it in Variables & secrets.
oauth2 must be resolved to a bearer token before sendingThe request uses OAuth and no token has been obtained yet. Authorize from its Auth tab.

A run does not stop at the first failure — every request is attempted, so one missing secret does not hide the state of the other seven.