NEW: Import and export tests as YAML. No vendor lock-in.

Close announcement
Logotyp bugbug.io
DemoPricing
Log inSign up
No vendor lock-in

Record tests visually.  Own them as YAML.

Finally, QA and developers share one test language. Record visually, export to readable YAML, and keep your tests versionable and portable.

Start testing. It's free
Human-readable
Diff-friendly
Schema-validated
Available on all plans

Visual editor

  • NavigateGo to /login
  • TypeType "qa@acme.com"
  • ClickClick "Sign in"
  • AssertAssert dashboard visible

Exported YAML

test: Sign in
steps:
  - goto: /login
  - type:
      value: qa@acme.com
  - click: Sign in
+ - assert: dashboard visible

TEST IMPORT & EXPORT

Visual testing without vendor lock-in

Create tests the easy way, then keep them as human-readable files your team can review, version, back up, and work with outside BugBug.

Own your test files

Export individual tests as YAML or download your whole project as a ZIP — so you always have a copy of your test assets.

Bring tests back anytime

Import tests or restore a complete project without rebuilding your regression coverage from scratch.

Review tests like code

Readable YAML makes every step and selector easy to inspect, diff, and review in pull requests.

No vendor lock-in

Keep tests outside the visual editor. Store them in Git, track changes, and keep an independent backup.

BugBug export test dialog offering YAML or ZIP with components
Read our documentation

Numbers QA teams hit with BugBug

Read customer stories

~90%

Reduction in time spent on repetitive regression testing

5x

Faster test creation than writing scripts from scratch

~70%

Less time spent fixing tests after every app update

Brand24UpfluenceVimondDattakZoovuAFS LogisticsSkribbleEmporixNewcode.aiSteppingblocksFitonMangoApps1902 SoftwareStartquestionBrand24UpfluenceVimondDattakZoovuAFS LogisticsSkribbleEmporixNewcode.aiSteppingblocksFitonMangoApps1902 SoftwareStartquestion

TEAM-SHARED TESTING

One test. The right interface for every role.

Product teams work visually. Developers work with structured files. Both contribute to the same regression assets, so nobody has to translate a recorded flow into a second test suite.

Product teams

Record critical workflows in the browser with visual test recorder. Read every step. Keep control of test intent.

QA engineers

Use reviewable definitions, reusable standards and environment references. Connect the suite to CI without rebuilding it.

Developers

Inspect structured diffs, review changes in Git and work with the same assets through YAML and APIs.

How it works

From visual recorder to engineering workflow

See how import/export works

Step 01

Record tests visually

Record browser workflows and add assertions without writing code.

Step 02

Export YAML

Export tests as readable YAML or whole projects as ZIP.

Step 03

Review and version

Store YAML in Git, review diffs, and use it in engineering workflows.

Step 04

Import and run

Import tests back into BugBug and run them locally, in the cloud, or through CI.

BugBug YAML test file showing schema version, component name and a goto step

WHY YAML FORMAT

More than a backup file

YAML turns recorded flows into inspectable, dev-compatible test assets.

Readable definitions

See test steps, assertions and reusable parts in a structured format.

Structured diffs

Understand exactly what changed before a test update is approved.

Environment references

Keep environment-specific values visible and manageable.

Reusable standards

Apply shared components and conventions across the suite.

Version control

Keep test history in the same review workflow as product changes.

APIs, CI and AI workflows

Let engineering systems and approved agents work with structured test assets.

Learn about YAML schema

No vendor lock-in

Your work stays yours

Export your suite. Keep the YAML in your repo. Continue to inspect, version and work with your test definitions outside the recorder.

Keep your files

Your exported YAML remains yours, even if you leave BugBug.

Keep access

Your BugBug workspace, flows, reports and elements stay accessible.

Come back anytime

Paid execution pauses; your work does not disappear. Return and continue where you left off.

Visual editor

  • NavigateGo to /login
  • TypeType "qa@acme.com"
  • ClickClick "Sign in"
  • AssertAssert dashboard visible

Exported YAML

test: Sign in
steps:
  - goto: /login
  - type:
      value: qa@acme.com
  - click: Sign in
+ - assert: dashboard visible

FAQ

Questions you may have

A human-readable representation of your test assets, designed for review, versioning and re-import.