The Reflog: launch week

We launched Composal on 29 October. Here is everything new in Verify since then, along with the big features we finished in the run-up to launch and haven’t written about yet.

Tests that learn from every pass

When a Scenario passes, Verify remembers how it passed. The next run replays those steps directly and only brings the AI back in when your app has changed. Runs get faster and cheaper the more you use them, and a Scenario that has fully learned your app can finish without calling the model at all.

You can see this happen. Every step is marked Learned, Healed or AI, live and in the recording, and you can open any step to see exactly what Verify did.

Here is the real thing, a run from our demo project. The Scenario checks that sharing a note gives a read-only link, and every step was replayed from what Verify learned last time.

composal.com · Acme Notes · Test run

Learning is shared, too. Verify learns how each test account signs in once, then reuses it across Scenarios, Discovery, Deep Scan and every PR preview. A brand-new pull request starts with everything earlier runs already learned.

Scenarios with more than one person in them

Plenty of real flows involve more than one person. An owner shares a note, a teammate opens it, and once the owner revokes the link the teammate should be locked out. You can now test that whole story.

Scenarios can depend on each other, and each person gets their own browser. Data flows between them, so the teammate opens the exact link the owner copied. The run page shows the full timeline, which step ran when, and how the runs connect.

Record a Scenario in your browser

Some journeys are quicker to show than to write down. Run:

com verify scenarios record --guided

A private Chrome window opens on your machine. Click through the journey, and Composal writes it up as a Scenario for you to review, run and upload. Press Ctrl+Shift+M on anything that must be there, and the recording adds a check for it. Recordings can be up to 1,000 steps long, and passwords are never saved into the file.

name: Create a note
persona: Owner
steps:
  - Open Notes.
  - Choose New note.
  - Enter title Weekly sync.
  - Choose Save.
  - 'Required check for "Weekly sync": the note shows in the Notes list.'

The recorder is available on Linux now, with macOS coming next.

For QA teams there is also Composal Recorder, a Chrome extension. It records across tabs, windows and sites, turns file uploads into steps, and lets you submit the Scenario and watch it run from the side panel. It’s in early access.

Discovery and Deep Scan, much bigger

Discovery explores your app and finds what’s worth testing. Deep Scan hunts for bugs. Both got a lot more room:

• Limits doubled. A scan can now run for up to 12 hours with up to 200 testers and 96 browsers at once. On plans with a larger browser allowance, scans also default to 4 hours, 40 testers and 20 browsers.
• Plans no longer cap how many browsers run in parallel, so a scan uses as many as its budget allows.
• Deep Scan testers now bring QA and security know-how, and each one has its own throwaway computer where it can write and run code while it investigates.
• Discovery keeps exploring until its time is up instead of stopping after a set number of turns.

Every Deep Scan now ends in a proper report: a written account of what was tested, every finding, coverage charts, and a library of the screenshots and videos behind it. Each claim links straight to the moment it was seen, and you can export the whole thing as Markdown.

CoverageFindingAll scans

composal.com · Acme Notes · Deep Scan

Coverage charts show what was checked, what found issues, and what is still unknown.

You can also watch a scan as it happens. The Discovery page shows what’s running now, who each run signed in as, and what it has found.

Getting started takes minutes

The easiest way to set up Composal is to let your coding agent do it. Copy one prompt, and the setup page ticks off each step as your agent finishes it. Your workspace name is filled in for you, and setup moves on to your repository as soon as your app is added.

Your first Discovery is included and starts testing as soon as your test account is ready. While it runs, every new workspace has a demo project of real test runs to look through.

A browser agent that handles more of the web

Verify now copes with more of what real apps throw at it:

• apps on plain HTTP, IP addresses and internal hostnames
• Google accounts with a password and two-factor sign-in
• success messages that only show for a second
• tabs that open on other domains
• evidence further down the page, which it now scrolls to find
• popups, extra windows, and search boxes inside in-app editors

Browser sessions API

You can now get a browser that stays open between requests, over HTTP or as MCP tools. Drive it directly with full Chrome DevTools control, or give it instructions in plain English. Screenshots and video come with it. See the browser API docs to get started.

Early access: Product Map and the scenario writer

Product Map turns everything Verify has seen into a map of your app. It opens as a library of your app’s flows, each with its key screens in order. Pick a screen to follow where it leads, one step at a time, or open the full map when you want the big picture.

composal.com · Composal · Product Map

The scenario writer makes Discovery’s suggested Scenarios more dependable. Each new Scenario is tried on your real app first, fixed if it doesn’t work, and only added to your list once it has run cleanly.

Both features, and the Composal Recorder extension, are rolling out to early access customers. If you’d like to try them, get in touch.

The Reflog comes out every week. If something here helped, or you’d like to see something next, tell us.