Provar docs

Welcome. If you've just installed the editor, jump to the quickstart — you can have a passing test in about five minutes, which is roughly the time it takes to read this paragraph and find a coffee.

This guide exists for the rest of the time: when you've forgotten a detail, hit a weird edge case, or want to understand why something is the way it is. Read it top to bottom on day one, then keep it open in a tab for the inevitable "wait, how do I…".

Core concepts

Three ideas, and once you have them the rest of the tool is just buttons.

A folder with your application and a .provar/ directory inside. Everything Provar cares about lives there — your files, the snapshots, the AI-generated scripts, the config. Outside that folder Provar doesn't look. That means no separate workspace, no cloud sync, no 'Provar account' — your tests are just files in your repo, reviewable in pull requests alongside the rest of the change.

Products

Provar ships as two artifacts. They're meant to be used together, but they have very different shapes — so they get their own quickstart and their own system requirements. Pick the one that matches how you work.