Search
Features
How individual Functionize Studio features work - self-healing and timing, workflows, extensions and reporting.
-
Self-Healing and Timing: Controlling How Studio Recovers
Studio adapts tests when your application changes — it finds a moved or renamed element instead of failing on a broken selector. How hard it tries, and how long it waits before giving up, are things you control. This article explains those settings, whe...
-
Workflows: Scheduled Jobs Written in Plain Language
A workflow is a recurring job described in plain language and run on a schedule. Where a test proves your application behaves correctly, a workflow just does something in a browser and reports back — checking a competitor's price, pulling a figure off a...
-
Extensions: Running Your Own Code Inside a Test
An extension is a piece of your own code that a test can call mid-run. Most tests never need one. When you do need one, it is usually because a step has to do something a browser cannot: decrypt a token, call an internal API, transform a value, read a f...
-
Reports: Pass Rates, Trends and What They Actually Tell You
Reports answers one question across everything you run: is testing getting better or worse? It is the only screen in Studio that looks across projects rather than at a single test. Tip: click any screenshot to open it full size. What is on the page O...