Starting and checking the app

An experienced developer doesn't say "done" without opening the app. Neither does Coodoo. After every task, Coodoo starts your app, looks at it and passes what it sees on to the developer and the reviewer.

This is on by default. You turn it off under Autopilot settings → Start and check the app.

What Coodoo checks

A website or web app

Coodoo starts your app (for example with npm run dev) and opens the pages in an invisible browser. It checks:

• whether the page loads;
• whether there are errors in the console;
• whether any parts (scripts, styles) fail to load;
• whether the page stays empty;
• what it looks like: it takes a screenshot of each page.

On top of that, it asks the app for files that should never be public, the way an attacker would: .env and .git. See Security.

A command-line program

Coodoo runs it with --help and checks that it answers properly.

A library

A library has no screen. The tests do the checking there, and this step is skipped.

What happens with the result

• If the app doesn't work, the developer fixes that first, before the review starts.
• The reviewer gets the report and the screenshots, and can reject the task if it doesn't look right.
• In the log you'll see something like ✔ App started and checked: the page loads without errors.

The report and the screenshots are in .coodoo/run-check/ in your project. Open them through the Project panel.

Safety limits

Every step has a time limit, and the app is always stopped again after the check. Coodoo opens the pages in a separate, empty browser with no cookies and no access to your camera, microphone or other permissions.

If it doesn't work

• The app doesn't start or doesn't respond? Check in the App panel which start command Coodoo uses; see Starting your app.
• Does your app need a database or another service to start? Describe that in a goal, or have the team write it down in .coodoo/run.json.