App settings

An app’s settings are where you brief Tada, the way you would brief a new QA engineer: where the app runs, who to sign in as, and when to check.

Overview

Open an app, then Settings. Each app has these pages:

Page	What it holds
General	The app itself, and removing it from Tada.
Cast	The people Tada plays in the app, and how each signs in. See The cast.
Environments	Each address the app runs at, and how Tada signs in there.
Schedules	When Tada checks an environment by itself.
GitHub	The repository, and what Tada read from it.

The app’s Overview is for seeing what happened: its checks, its open issues and what Tada has learned. Setup lives in Settings.

Environments

An environment is one address your app runs at, such as staging or production. Tada finds them in your deploy history. If it cannot, press Type an address instead.

Each environment has its own sign-ins, because each usually has its own database. There are three ways to give Tada one:

• Connect a sign-in. Tada opens your app in a browser on its side. You sign in once, the way you always do, and checks on that environment start already signed in. This works for apps that sign in with Google or Microsoft, and it asks nothing of your code.
• An email and password that your seed creates in every environment. Tests type it with placeholders, so no password is stored in a test. See Test file syntax.
• A test user Tada makes for itself. See The cast.

A saved sign-in works only at the address it was saved on, and sign-ins expire. When one stops working, Tasks tells you and offers Sign in again.

Schedules

An environment can be checked on a schedule: Every day, Twice a week, Every week or Every month. A scheduled check covers every feature on that environment and counts toward your plan like a check you start.

A schedule can point at a live site. There Tada leaves out any test that presses something that sends, saves or deletes.

GitHub

• Tada checks deploys to staging and to pull request previews. See Checks on pull requests.
• Ask GitHub again re-reads environments, addresses and any test files your team committed. It never overwrites anything you set.

The note in your repository

.tada/rivet.md is an optional note in your repository that tells Tada how your app works: where it runs, how to sign in, the traps that cost a person an afternoon, and the data your seed guarantees. Rivet reads it before she writes a test. Tada reads it at the commit that deployed.

Name a login in the file, never its password. Anyone who can read the repository can read the file.