Search
Functionize Studio
Studio Basics
-
Start Here
Everything we have written about Functionize Studio, on one page. Pick the box that matches what you are trying to do.New to Studio? Work down the left column: Studio Basics to understand it, then Exercises to actually build something. Studio Basics W...
-
What Is Functionize Studio?
Functionize Studio is an independent testing agent for your web application. You describe what should be true in plain language; Studio builds the test, runs it in a real browser, tells you what happened, and keeps it working as your application changes...
-
Getting Started
Functionize Studio lets you create, run and maintain tests by describing what you want in plain English. This guide covers what it is, how to phrase your first request, and what the agent does with it. Open in Studio Open Studio in a second tab and work...
-
Starting a Session: The Studio Home Screen
Most people meet Studio through a project, but the Home screen is the fastest way in. It is a single prompt box that can create a test, connect an internal site, or start any other job — without you deciding up front which of those you are doing. Open i...
-
Your First Test in Functionize Studio: A Visual Walkthrough
This is a picture-by-picture walkthrough of creating your first test in Functionize Studio, from an empty project to a green run. Every screen below is the real product, working against the Functionize demo store, so you can follow along exactly without...
-
Understanding a Test Run and Its Results in Functionize Studio
A test run in Functionize Studio produces more than a pass or a fail. Every step keeps a screenshot of the page as it was, the values it read, and a comparison against the last time the test succeeded. This article explains how to read all of that, and ...
What's New
-
What's New in Functionize Studio
Everything below has shipped and is available to you now. This page is updated every Friday, newest first, so you can see what changed without reading a release note that assumes you already know the product. Each entry says what it is, and then the pa...
Onboarding
-
A Map of Studio: Every Screen and What It Is For
Studio has nine screens in the sidebar and about a dozen places where real work happens. Nothing about it is hard once you know what each screen is for, but for the first week most people bounce between two of them and never discover the rest. This is ...
-
Your First 30 Minutes with Functionize Studio
The single biggest predictor of whether a team sticks with Studio is whether the first half hour produces something real. This page is that half hour, deliberately sequenced so you get a passing test before you have to make any decisions. Open in Studio...
-
Before You Point Studio at Your Own Application
Most first-week failures are not testing problems. They are access problems: Studio cannot reach your application, or reaches it and sees something a real user would not. This page is the checklist to work through before you write tests against your own...
-
Choosing What to Automate First
Teams that stall with test automation rarely stall on the tool. They stall on choosing what to automate, automate the wrong things first, and lose confidence before the suite becomes useful. Watch: Functionize Studio 101: Ask Studio What to TestThe same...
-
Your First Two Weeks: An Onboarding Plan
A day-by-day plan for getting a team genuinely productive, not just logged in. It assumes one person leads the rollout and two or three others follow a week behind. Open in Studio The screens this plan walks you through. Links open in a new tab. Studio...
-
What to Measure: QE Metrics and KPIs with Studio
Tear sheet — What to MeasureA printable two-page handout of everything on this page: a week-one baseline worksheet to fill in, the seven KPIs with their targets and sources, the reporting rhythm, first-quarter targets and the three numbers that justify...
Adoption
-
How It All Ties Together: Studio Across an Enterprise
Studio is easy to try with one person and one test. Getting it working across an enterprise — several applications, several teams, environments that differ, people who have never met each other's tests — needs you to understand how the pieces fit. Open ...
-
Inviting Your Team and Working Together in Studio
Getting other people into Studio is the easy part. Getting them in at the right moment, into a workspace that already works, with conventions agreed before anyone writes their fortieth test — that is what decides whether adoption takes or stalls. Open i...
-
Naming, Tagging and Not Drowning: Conventions for a Shared Account
Studio accounts do not fail slowly because the product runs out of room. They fail slowly because nobody can find anything. Here is what a real, actively used Studio account looks like after a few years: around 1,900 projects, 2,800 sessions, 1,260 orc...
-
Testing End-to-End Across Several Web Applications
Enterprise journeys rarely stay inside one web application. An order placed in a storefront appears in an order-management system and again in a finance tool. A new starter created in an HR system shows up in a directory, a payroll application and a tic...
-
Scaling From One Team to Many
The pilot worked. One team, one application, a suite people trust. Now three more teams want it, and the question is no longer whether Studio works — it is whether what you built can be repeated without fragmenting into four incompatible ways of doing t...
Exercises
-
Start Here: The Functionize Studio Exercise Series
This is a self-paced series that teaches Functionize Studio by building something. You work against our own demo store, so you can follow every step exactly without touching your own application, and nothing you do here can affect a real system. Open in...
-
Exercise 1 - Create Your First Test From a Prompt
Lab handout — Lab 1A printable worksheet for this exercise: the tasks, the exact prompts, a checkpoint and stretch challenges. Hand it round when you are onboarding a team.Download the PDF (102 KB) In this exercise you will describe a test in one sente...
-
Exercise 2 - Write Assertions That Prove Something
Lab handout — Lab 2A printable worksheet for this exercise: the tasks, the exact prompts, a checkpoint and stretch challenges. Hand it round when you are onboarding a team.Download the PDF (98 KB) A test that clicks through a flow without checking anyt...
-
Exercise 3 - Read a Test Run and Its Evidence
Lab handout — Lab 3A printable worksheet for this exercise: the tasks, the exact prompts, a checkpoint and stretch challenges. Hand it round when you are onboarding a team.Download the PDF (85 KB) A run keeps far more than a pass or a fail. This exerci...
-
Exercise 4 - Change a Test by Asking
Lab handout — Lab 4A printable worksheet for this exercise: the tasks, the exact prompts, a checkpoint and stretch challenges. Hand it round when you are onboarding a team.Download the PDF (98 KB) Tests are not finished when they first pass. Requiremen...
-
Exercise 5 - Break a Test on Purpose, Then Diagnose It
Lab handout — Lab 5A printable worksheet for this exercise: the tasks, the exact prompts, a checkpoint and stretch challenges. Hand it round when you are onboarding a team.Download the PDF (74 KB) Everyone can read a green test. The skill worth having ...
Best Practices
-
Flutter Readiness Checklist
Functionize Studio now tests Flutter web applications end to end. Flutter draws its interface onto a canvas instead of standard HTML, so Studio reads your app through Flutter's semantics tree, the same layer screen readers use.The four steps below make ...
-
What Makes a Good Automation Candidate
The single most expensive mistake in test automation is not a bad tool. It is automating the wrong things, discovering it six months later, and concluding that automation does not work. Open in Studio Your existing projects and tests, to score against. ...
-
Writing Prompts That Produce Durable Tests
The quality of a Studio test is decided almost entirely in the sentence you write to ask for it. Not by the tool, not by the application, and not by how long you spend editing afterward. Open in Studio Try a prompt for real. Links open in a new tab. St...
-
Reviewing AI-Generated Tests: What a Human Still Has to Check
An agent can write a test faster than you can read one. That asymmetry is the productivity gain, and it is also the risk: it is entirely possible to acquire four hundred tests in a week, none of which would notice if checkout broke. Open in Studio Open ...
-
The Independent Tester Principle: Never Build and Test in the Same Session
If you take one practice away from this section, take this one: never let the same AI session that wrote the code also write and judge the tests for it. Open in Studio Where the independent tests end up. Links open in a new tab. Studio Home ↗Tests ↗MCP...
-
Setting Up an Adversarial Test Loop With Claude and the Functionize MCP Server
The previous page argues that the agent which wrote the code must not be the agent which tests it. This page is the setup: two sessions, two models, one of them pointed at Functionize over MCP, and a loop that runs every time you ship. Open in Studio Se...
Templates
-
Test Strategy Templates You Can Use Today
Strategy documents you can download, edit and put your own name on. They exist because the hardest part of getting an automated testing layer working is rarely the tool — it is agreeing, in writing, what you test, why, and who owns a red result. Open in...
-
Master Test Strategy Template
Master Test Strategy — templateBoth formats: the Word file is the one you edit, the PDF is for reading, printing and circulating. Adapt them freely — once you download them they are yours, and there is nothing to attribute.Download Word (.docx) · 67 KB...
-
Integration Test Strategy Template
Integration Test Strategy — templateBoth formats: the Word file is the one you edit, the PDF is for reading, printing and circulating. Adapt them freely — once you download them they are yours, and there is nothing to attribute.Download Word (.docx) · ...
-
Regression Test Strategy Template
Regression Test Strategy — templateBoth formats: the Word file is the one you edit, the PDF is for reading, printing and circulating. Adapt them freely — once you download them they are yours, and there is nothing to attribute.Download Word (.docx) · 6...
-
User Acceptance Test Strategy Template
User Acceptance Test Strategy — templateBoth formats: the Word file is the one you edit, the PDF is for reading, printing and circulating. Adapt them freely — once you download them they are yours, and there is nothing to attribute.Download Word (.docx...
-
Testing an SAP S/4HANA Transformation
Moving from SAP ECC to S/4HANA generates more manual test execution than almost any other program a business will run. Four named test levels, several cycles each, repeated at every wave and every transport — and most of it executed by hand, often by a ...
Value Calculators
-
Value Calculators: Building the Business Case
Two spreadsheets that turn a testing decision into a number a finance reviewer will accept. Both are free to download, edit and put your own name on, and both are built so that every assumption is a cell you can see and change — there are no constants h...
-
Manual to Automated: What the Change Is Worth
For a team whose regression testing is mostly done by hand. This calculator values the hours you stop spending and the defects you stop shipping, then sets both against what the change costs you in year one — including the effort to build the suite, whi...
-
Baseline and Improve: Valuing a Change in Tooling
For a team that already automates. Rather than comparing claims, this calculator asks you to measure: five numbers on what you run today, the same journeys on Functionize for a fixed period, the same five numbers again, and the difference valued in mone...
Features
-
Projects: Boundaries, Defaults and What Inherits What
A project is the container for tests that share an application, an environment and a set of defaults. It is the least glamorous object in Studio and the one that causes the most trouble when it is drawn badly, because almost everything else inherits fro...
-
The Tests Screen: Finding, Tagging and Fixing Tests at Scale
Every test you or anyone else has built lives on one screen. For the first couple of weeks that screen is a convenience. By the time an account holds a few thousand tests it is the main way anybody finds anything, and the habits you form early decide wh...
-
Test Data: Execution Presets, Variables and Secrets
Tests need data: a price to check against, an account to sign in with, a reference number a later step depends on. Studio keeps that data out of the test itself, so the same tests can run against different environments and so secrets never end up writte...
-
Orchestrations: Running a Suite as One Job
A test tells you about one flow. An orchestration tells you whether the application still works. It is an ordered group of tests that runs as a single job, on demand or on a schedule, with one result and one history. This is the feature that turns a co...
-
Scheduling an Orchestration: The Six Cadences and What Each One Costs
An orchestration's schedule is the single setting that decides what it costs and whether anyone still trusts it in six months. Everything else about a suite — which tests, what order, who gets the email — matters less than how often it runs. There are ...
-
Run Order, Re-runs and Alerts: An Orchestration's Advanced Settings
The New Orchestration panel has four fields you cannot miss and two collapsed sections you easily can. Advanced settings is the second of them, and it holds four decisions that change what a suite does when something goes wrong. None of them are requir...
Settings
-
Settings: Where Everything Lives and What to Change First
Studio's settings sit at two levels — project and test — with the same structure in both. This article maps every section so you know where to look, and explains the one idea that makes the whole thing make sense: defaults at the project, exceptions at ...
-
Timeouts, Access and Browser Behavior: Getting Studio Into Your Application
Most applications worth testing are not a public website with no front door. They sit behind authentication, use client certificates, need particular cookies, or are simply slow. This article covers the settings that get Studio into your application and...
Skills
-
Why Context Matters, and How to Give Studio More of It
The fastest way to get good tests out of Functionize is not a better prompt. It is giving the agent the context a new colleague would need — what your application is for, who uses it, what the words mean, and which parts are quietly treacherous.What eac...
-
Why Skills Matter — Giving Your AI Agent the Context It Needs
An AI agent pointed at your application knows everything about software in general and nothing about yours. It does not know that a "wavelength carrier" is a real thing in your world, that your Save button quietly refuses duplicates, or that the third d...
-
Functionize Skills: What Is Available and How to Install Them
Functionize publishes a library of ready-made skills — briefings that teach your AI tool how a particular application works, so it can write good tests for it straight away. There are skills for Salesforce, SAP, Workday, ServiceNow, Microsoft 365 and mo...
-
How to Build a Skill in Claude for Your System Under Test
A skill is a short document that teaches Claude about one of your applications, so that anyone on your team can ask for a test in plain English and get one that already understands your domain. This article shows you how to write one, with a complete wo...
-
Complimentary Skill Building for Your System Under Test
An AI agent that knows nothing about your application has to discover it — one wrong turn at a time. A skill fixes that. It is a package of context about your specific system under test that makes the agent competent in your application from the very fi...
Model Context Protocol (MCP)
-
Getting Started with the Functionize MCP Server
The Functionize MCP server lets an AI client — Claude Code, Claude Desktop, Gemini CLI, or anything else that speaks the Model Context Protocol — work directly with your Functionize agent sessions. You can start a session, send it messages, stream its e...
-
Connect Claude Code to the Functionize MCP Server
Claude Code speaks HTTP MCP and OAuth natively, so connecting it to Functionize takes one command and a sign-in. There is no bridge to install and nothing to copy and paste back into the terminal. Open in Studio Copy your connection details from here. L...
-
Connect Claude Desktop to the Functionize MCP Server
Claude Desktop connects to the Functionize MCP server natively, through its Connectors settings. Nothing to install, no configuration file, no Node. Open in Studio Copy your connection details from here. Links open in a new tab. MCP ↗ This is the verifi...
-
Connect Cursor to the Functionize MCP Server
Cursor connects to the Functionize MCP server directly. It speaks Streamable HTTP and handles OAuth itself, so there is no bridge to install and no Node.js requirement. Open in Studio Copy your connection details from here. Links open in a new tab. MCP ...
-
Connect VS Code and GitHub Copilot to the Functionize MCP Server
VS Code connects to the Functionize MCP server natively in GitHub Copilot's agent mode. It handles Streamable HTTP and OAuth itself — including registering with our server automatically — so there is no bridge and no Node.js requirement. Open in Studio ...
-
Connect Gemini CLI to the Functionize MCP Server
Gemini CLI connects to the Functionize MCP server natively. It speaks Streamable HTTP, discovers our OAuth configuration on its own, and opens your browser to sign in. No bridge, no Node.js requirement beyond Gemini CLI itself. Open in Studio Copy your ...
Non-Public Application Testing
-
Functionize Quickconnect (ACS Quickconnect)
QuickConnect is a small, portable desktop application. It creates an end-to-end encrypted connection between Functionize's test-execution engine and the user's computer, so automated tests can reach applications on the user's internal network. It runs ...
-
ACS Quickconnect Data-flow Diagram
A complete data-flow diagram of how the QuickConnect desktop agent (and the ACS agent) connects a customer host to the Functionize platform, annotated with every protocol, port, and TLS version. It's built to hand to a customer's networking/security tea...
Glossary
-
AI Testing and AI-DLC: A Glossary
The vocabulary of AI testing is moving faster than anyone's ability to standardize it. Terms get coined in a blog post, picked up by vendors, and are load-bearing in a procurement document six months later — often meaning three different things to the ...
-
The AI-Driven Development Lifecycle: Terms
The vocabulary of building software with AI agents — the lifecycle framings, the practices, the artifacts, and where verification sits inside them.What this page covers, and four things to be precise about when you say AI-DLC. ABCDEFGHIJKLMNOPQRSTUVWXYZ...
-
Agentic Systems: Terms
The vocabulary of agents themselves — how they are built, what they remember, how they connect to your systems, and the named ways they fail.What this page covers, and four terms that quietly invalidate a test strategy. ABCDEFGHIJKLMNOPQRSTUVWXYZ A Agen...
-
Evaluating and Testing AI: Terms
The vocabulary of proving an AI system works — evals, judges, groundedness, red teaming, and the statistics you need when a test case is a distribution rather than a pass or a fail.What this page covers, and the one difference that changes how you test....
-
Quality Engineering and AI Assurance: Terms
Classic quality-engineering vocabulary restated precisely, because AI vendors blur it — plus the governance, standards and regulatory terms that now touch testing.The four groups of terms on this page, and the five that most often get misread. ABCDEFGHI...