Checks before the build

LobLogix writes checks from your agreed specification before the application is built, so the finish line is fixed first.

What a check is

A check is a statement the finished application must satisfy. On screen they are called Battery Tests, grouped into suites. You find them in the TDD & QA tab.

There are three kinds:

• Happy Path. Things that should work, such as recording a booking.
• Errors. Things that should be refused, such as booking an item twice for one day.
• Integration. Several steps in a row, such as book, collect, return and close.

Why they come first

Checks written after the build tend to describe what was built. Checks written from the agreement describe what you asked for.

You approve them

The checks are proposals until you review them. You read each one against the capability it covers, then lock the set. Locked checks cannot be changed quietly, by a person or by the assistant.

Tied to a version

Each set of checks is tied to the exact snapshot of the specification it was written from. This is called a pin. If a newer snapshot of the specification reaches production, the suite is marked newer Living Spec, so you know the checks are out of date.

What happens next

The application is built and run against the locked checks. See How checks are run, and what a pass means.

To write and lock your own, see Write, review and lock your checks.