QuintStudio

Your guide to:
Preserving behavior across changes

First, we discover and decide on how the code should behave.
Then, we make sure there are enough tests to enforce this behavior.

Step 1: Scan your codebase

Studio maps code into components with the right scope for it to work from.

Step 2: Pick one or more component to get started

12 CARDS

Studio recommends where to start from, but it's ultimately your choice.

Step 3: Confirm the behavior

BEHAVIOR

A few minutes:

Review behaviors individually, one concern at a time.

Go deeper:

Build a Quint model which captures all possible behaviors in scope.

This step often surfaces unexpected behaviors. Studio can help you fix any of these you mark as bugs.

Step 4: Check the tests against the behavior, and find blind spots

transfer.test.tslimits.test.tsno test holds this

Every confirmed behavior or interesting trace from the Quint model is either linked to real tests or flagged as a blind spot.

Step 5: Cover the blind spots

transfer.test.tslimits.test.tsapprove.test.tsexpire.test.tspushed backblind spotbalance.test.tsrefund.test.tsretry.test.tsslips through the gap

Every behavior-associated test is a segment of the rail. A blind spot is a gap in the rail, until Quint Studio generates a test that closes it.

Quint Studio is a local tool

YOUR MACHINEyour codespecscoverageyour codingagentsQuint Studioruns hereanonymous telemetryQuint serversagent datayour agentprovider

Quint runs locally on your compute, driving coding agents you already have. The only things that ever leave your machine are anonymous usage telemetry and your agents' own traffic to your agent provider.
Code, specs, and coverage are never shared with Quint.

Quint Studio is in Beta

We hope you have a good experience with our beta.
If you face issues or have feature requests, please don't hesitate to reach out!
Email us at contact@quint.sh or schedule a call via the in-app help center.