TestingOps.ai

Design tools · Native connection

Figma and TestingOps: test cases from your screens

TestingOps reads the frames of a Figma file, page or section, with their texts, controls and prototype links, so its AI test agents can prepare test cases while the feature is still in design.

  • Native connection
  • Available
Request a demo Figma: manage personal access tokens
Connection
Native connection
Writes back
Nothing, it only reads
Last checked
7 Nov 2026

In short

Figma and TestingOps in short

The Figma connection reads the screens of a Figma file, page, section or single frame through the Figma REST API with a personal access token, and writes one knowledge-base document per screen: its texts in reading order, the controls named in its layers and its prototype links.

TestingOps agents use these documents as context when they write and review test cases, so test preparation can start before the feature is built.

The connection is read-only and gives context only: it produces no runnable UI tests, no scripts and no visual comparison against the design.

You need a token with the File content and File metadata read scopes; a file shared as "Anyone with the link can view" can also be analysed from its prototype link without a token.

What it does

What it does for your testing

  1. 1

    Screens become step context

    Input
    Top-level frames of a file, page, section or a single frame
    TestingOps
    Writes each screen's texts from top to bottom, the controls its layer names identify (buttons, inputs, dropdowns, checkboxes, tabs, links) and a link back to the frame
    Output
    One knowledge-base document per screen that agents read while writing steps and expected results
  2. 2

    Prototype links become journeys

    Input
    Prototype interactions and connectors between frames
    TestingOps
    Records each transition as element → target screen, for example "Continue" → screen "Payment"
    Output
    Paths across screens that agents can turn into end-to-end scenarios
  3. 3

    FigJam notes are kept

    Input
    Stickies, texts, shapes and connectors placed directly on a page or a FigJam board
    TestingOps
    Collects them into one notes document per page
    Output
    Workshop decisions and open questions next to the screens they concern
  4. 4

    Shared prototypes without a token

    Input
    A prototype shared as "Anyone with the link can view"
    TestingOps
    Opens the prototype view in a browser on the TestingOps server and has the project's image-capable model describe each frame
    Output
    Up to 25 screen documents with fields, actions, texts, validation messages and navigation

Step by step

How it works

  1. Connect with a personal access tokenSave a Figma personal access token with the File content and File metadata read scopes under Integrations → Project tools → Design tools → Figma. Add a team page link if you want to pick files from a list.
  2. Link a file, page or frame to a projectIn the project's Knowledge Base, add a Design tools source: pick files or paste links. A frame or section link brings only that part; a file link brings every screen, up to 200.
  3. TestingOps checks the version firstEach sync asks Figma for the file version. When it has not changed, no screens are read again, which spares Figma's limited file reads.
  4. Screens become documentsEvery screen becomes one document. A changed screen replaces its old document, and the document of a deleted screen is retired.
  5. Agents write and review test casesAgents search these documents while they write and review cases. The cases then run like any other case on your execution provider; on testingops.ai that is RunningOps.

Designs are reference material here. Nothing in this flow produces runnable UI tests or scripts, and no run is compared with a Figma frame.

Connect

Setup

  1. In Figma, create a personal access token with the File content and File metadata read scopes (Settings → Security → Personal access tokens).
  2. In TestingOps, open Integrations → Project tools → Design tools → Figma, paste the token and, optionally, a team page link.
  3. Open Knowledge Base, pick the project, select Add source on Design tools, choose the Figma connection, select files or paste file, page or frame links, then select Link to RAG.
  4. Select Sync again on the linked source. Later syncs run automatically and skip files whose version has not changed.
  5. For a public prototype without a token, paste its link under Add a Figma link in the same dialog and select Add and analyse.

Documentation: Figma: manage personal access tokens · Figma REST API documentation

Where you connect it in TestingOps: Integrations → Project tools → Design tools → Figma

Use cases

Use cases

Prepare test cases while the feature is in design

Trigger
The screens of a new feature are ready for review in Figma
Uses
The frames of the feature's page, their texts, controls and prototype links
Agent activity
Plans scenarios along the prototype path and writes expected results with the exact copy shown on each screen
Result
Draft test cases for review before the feature reaches a test environment
Condition
Steps are confirmed on the running app once it exists; locators do not come from Figma

Pick up copy and flow changes

Trigger
Designers change labels, error messages or prototype links
Uses
The next sync, which re-reads the file because its version changed
Agent activity
Works from the replaced screen documents when it writes or reviews cases afterwards
Result
Agents see the current texts, not the ones from the first sync
Condition
Existing test cases are not edited automatically; reviewing them is a separate request

Work from a prototype someone shared with you

Trigger
An agency or another team shares a public prototype link
Uses
Up to 25 prototype frames, analysed from screenshots
Agent activity
Writes cases from the fields, actions, validation messages and navigation extracted for each screen
Result
One document per analysed screen, without a Figma account connection
Condition
Only the prototype view is readable; the analysis needs an image-capable model and counts toward your AI usage limit

Capabilities

Capabilities and limits

What is read

  • Screens: top-level frames, components and instances under pages and sections, for a whole file, a page, a section or a single frame
  • Per screen: texts in reading order, controls recognised from layer names (button, input, dropdown, checkbox, radio, toggle, tab, link) and prototype transitions
  • Items placed directly on a page, such as FigJam stickies, texts, shapes and connectors
  • Design, prototype, FigJam board, slides and branch links
  • Without a connection: the prototype view of a file shared as "Anyone with the link can view"

What is produced

  • One knowledge-base document per screen, with a link back to the frame
  • One notes document per page for items outside frames
  • From public links: one document per analysed screen with its name, purpose, fields, actions, texts, validation messages and navigation

Where it can write

Nothing in Figma. The connection only reads files.

How it connects

Figma REST API with a personal access token. Public links: Figma's public embed check, then the prototype view in a headless browser on the TestingOps server.

Account and permissions

  • A Figma personal access token with the File content and File metadata read scopes, from an account that can open the file
  • Preferably a token from a Dev or Full seat: Figma allows View and Collab seats about 20 file reads a month
  • Optional: a team page link, to pick files from a list
  • On testingops.ai, use a token: the Connect with Figma sign-in is not offered there

Limits

  • Up to 200 screens per sync; a larger scope is marked as truncated
  • Controls are recognised from layer names only: a component named "Rectangle 12" contributes its text but no control type
  • Public links: prototype view only (design views and FigJam boards are blocked for the server's browser), up to 25 screens, re-read only when you select Sync again
  • Each Figma connection counts toward your package's integration limit
  • No runnable UI tests, scripts or visual comparisons against designs

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A product team designs a new checkout in Figma and links the Checkout page to its TestingOps project. The Payment screen's document lists the card fields, a Pay now button, the error text of the declined state and a prototype link to Order confirmed.

An agent drafts cases for a successful payment and a declined card from those documents and quotes the on-screen messages in the expected results. The steps are confirmed on the running app when the feature reaches the test environment.

Frequently asked questions

Can TestingOps generate automated UI tests from Figma designs?

No. It reads screens into the knowledge base, and agents write test cases from them: steps and expected results that run as AI-executed steps on your execution provider. No scripts are generated from Figma, and runs are not compared with Figma frames; visual checks in TestingOps compare a step with an earlier run of the same step.

Which token scopes are needed?

File content and File metadata, both read. The token's owner must be able to open the file. A team page link is optional and only fills the file list.

Why does Figma answer 429 Too Many Requests?

Figma limits how often a token may read files, and for View and Collab seats it allows about 20 file reads a month. Use a token from a Dev or Full seat. TestingOps asks for the file version first and reads no screens when the version is unchanged.

Can I add a Figma file without connecting an account?

Yes, when the file is shared as "Anyone with the link can view": paste its prototype link under Add a Figma link and select Add and analyse. Up to 25 screens are analysed from screenshots by the project's image-capable model, which counts toward your AI usage limit. Design views and FigJam boards cannot be read this way. Reading through a token connection uses no AI model.

Are FigJam boards read?

With a token, yes. Stickies, texts, shapes and connectors placed on a page become one notes document for that page, and frames on the board are read like screens.

Can I sign in with Figma instead of using a token?

Not on testingops.ai today. The Connect with Figma button appears only where an administrator has registered a Figma OAuth app for the server, and testingops.ai has none, so use a personal access token.

How often does TestingOps re-read a file?

When you select Sync again on the linked source, and on the automatic sync, which runs hourly by default for token connections. Each time it checks the file version first and reads screens only when the version has changed. Public links are re-read only when you select Sync again.

Next step

Bring a Figma file from a feature that is still in design to a demo and see the screen documents your agents would write cases from.

Request a demoMore design tools integrations