Repository settings

Every setting on a repository's Settings page.

Open a repository's settings

Open the repository and click Settings. The page shows one section at a time: Coverage, Definition of done, Browser tests and Linear. Each section saves on its own.

These settings belong to one repository. Your account's settings, such as your plan and API tokens, are covered in Plans and limits.

Coverage

What verifAIed downloads from CI, and how the tests it asks for should be written.

  • Artifact name: the GitHub Actions artifact that holds your coverage report and junit.xml. The default is coverage. It must match the name: in your actions/upload-artifact step exactly, including case.
  • Testing conventions (optional): your testing style, such as the fixtures to use, naming patterns and how to mock. It is added to every prompt generated for this repository. Leave it empty to use the default conventions, or click Restore default to bring them back.
  • Coverage workflow: two example GitHub Actions workflows to copy, one for Python (pytest) and one for TypeScript (vitest), and a Setup prompt that has an AI model write a workflow for your stack. If you change the artifact name, change the name: in the workflow to match.

The status beside the heading reads Awaiting first CI run until verifAIed has picked up coverage from a workflow run, then CI run detected. CI coverage explains the workflow.

Definition of done

A list of switches, one for each kind of finding. A finding that is switched on blocks a branch from being done; one that is switched off is reported as a warning. Definition of done describes every switch.

Browser tests

How tests are recorded, how replay videos look and how many tests run at once. Reset all to defaults puts every setting back.

Recording

What happens while a test is being recorded in the studio.

SettingConfig keyDefaultWhat it does
Hold after each checkassertion_pause_ms2 seconds (2000 in the file, which counts milliseconds)How long the video lingers after a check passes, so a viewer sees what was checked. 0 for no hold. Any single check can be given its own.
Caption each step as it landscaptionsOnWrite a short plain-English caption for each step as it is recorded. Any caption can be edited or switched off afterwards.

Replay video

How a replay's video is paced and what is drawn on it.

SettingConfig keyDefaultWhat it does
Highlight before each actionreplay_show_actions_ms250 msHow long each step highlights the element it is about to act on, with the click point marked. 0 turns the highlight off.
Dwell after each stepreplay_slow_mo_ms0 msAn extra pause after every operation.
Cursor movereplay_cursor_ms400 msHow long the drawn cursor takes to cross the page to the next element. 0 draws no cursor.
Delay between keystrokesreplay_type_delay_ms200 msText is typed one key every this many milliseconds. 0 fills a field all at once.
Wait at pauses and holdsreplay_pausesOnWhether a test's Pause steps and the holds after its checks actually wait.
Draw captions on the videoreplay_captionsOnWhether each step's caption is shown while the step runs.
Page sizereplay_viewport1280x900The size of the page during a replay, and of its video, as width×height. Each side is 200 to 7680 pixels.
Name the test in a cornerreplay_video_step_bannerOnShow a banner with the test's name for the whole run.
Speed up runs nobody is watchingreplay_renderOnA Run all, a folder's Run and a CI run go at full speed, and the paced video is put together afterwards. Off paces them live, which is slower. A test you just recorded or run on its own is always paced live.

Running tests

How a batch of runs started from the Browser tests page is worked through.

SettingConfig keyDefaultWhat it does
Tests run at onceparallel_runs1How many tests a Run all or a folder's Run replays side by side, from 1 to 8. More than 1 needs an environment with no reset, or one that declares a copy of the app for each extra run. Recordings and single runs always take turns.

Which value wins

Every browser-test setting can also be written in your repository, in .verifaied/config.toml, under the config key in the tables above:

[browser-tests]
replay_viewport = "1440x900"
replay_type_delay_ms = 100

When the same setting is given in more than one place:

  • A choice made for one run wins over everything, for that run only: Video settings when you start a run from the web, or --video on verifaied test run.
  • A value saved on the Settings page applies to every machine that records or replays the repository, and wins over that machine's file.
  • A setting left on its default on the Settings page lets the machine's file decide.
  • If the file says nothing either, the default applies.

Replay videos shows what the video settings look like in practice.

Linear

Shows whether your Linear workspace is connected, so branches carry their Linear issue. See Linear.