Use case

A booking sitethat never double books.

Calendars, time zones and emails. Adams helps you ask the right questions up front and check the pages that customers use.

Lite and Pro
// the problem

What goes wrong

Time is harder than it looksA slot at 9 in one time zone is 3 in another. Daylight saving moves it again. A site that ignores this books people at the wrong hour.
Two people, one slotWithout a check in the right place, two visitors can reserve the same time and both get a confirmation.
// what adams does

What Adams does

Asks the unclear questionsPro: time zone, cancellation rules and who confirms are settled before the build starts.
Checks the booking flow on a phonePro: the date picker and the confirm button are checked at 375 pixels.
Keeps provider keys safeLite: calendar and email keys are caught before they are committed.
// worked example

An example

A date picker on a phone

Illustrative output.

~/project~/your-project · example
$ adams check http://localhost:3000/book
375px: the time slots overflow by 22px
375px: "Confirm booking" label wraps
Switching to a scrolling list
✓ 3 widths checked, no problems
// faq

Questions

Will Adams prevent double booking?

It does not test your database logic. It asks about the rule up front and a review can look for the missing check.

Can it check emails?

No. It checks text and pages. Send a real test confirmation yourself.

What is Pro here?

The questions, the page checks and the review. The key guards are Lite.

// related

Keep reading