baguette-test-app

Test an app with baguette

The test is a loop you do yourself, not a script you write:

read the screen → think what's next → click → check it worked.

Your judgment is the point. A script can only find what it was told to look for; you can notice that the price is wrong.

Before you start

baguette list --json                         # a booted UDID
baguette boot --udid <X>                     # if none is running
xcrun simctl install <X> path/to/App.app     # if it isn't installed

If the user wants to watch, start baguette serve and give them http://localhost:8421/simulators/<X>.

Write down what success looks like before the first click, in the user's words. "Signed up" isn't enough: "a new account, on the free plan, with the receipt emailed".

The loop

1. Open the app and read the screen, in one call.

baguette launch --udid <X> --bundle-id <id> --relaunch --then-describe-ui

It waits for the first real screen, usually 4 to 5 seconds. Baguette logs to stderr, so add 2>/dev/null if you only want the answer. This first answer also has how, the commands to use from here. Answers to a tap leave it out, because you just ran one.

2. Read the answer and think. It's short, and says what you can do:

{"ok":true,"changed":true,
 "affordances":{"tap":["Back","Groceries, 3 items","Holiday, 12 items","New List"]},
 "disabled":["Share List"],
 "text":["My Lists"],
 "values":{"Home":"1"}}

• affordances.tap: the controls you can tap, by name.
• affordances.type: a focused text field you can type into.
• affordances.adjust: a slider. A press can't set a value, so drag it with swipe, using its frame from describe-ui.
• disabled: controls that can't be used yet. Do what they're waiting for first.
• text: what the screen says. Some of it can be tapped too, like a Show more link.
• values: a control's value, like a switch's 1 or the selected tab's.

Read what's there before choosing: the first row is rarely the one the task means.