FEATURES
Why Flow²Test is powerful for API automation teams.
A capability catalogue — problems teams face, how Flow²Test solves them, and the outcomes you get. For the visual product tour, visit Product. For the getting-started path, visit How It Works.
Coming in v1.3
Enterprise Assertion Intelligence™
Transport Assertions
Validates status codes, methods, paths and protocol-level outcomes.
Business Assertions
Checks critical business fields and domain values beyond HTTP success.
Dependency Assertions
Confirms IDs, tokens and references flow correctly across API chains.
Relationship Assertions
Verifies request–response and cross-call relationships stay consistent.
Response Assertions
Asserts payload content, nested objects and expected response values.
Request Assertions
Validates outbound request shape, parameters and required inputs.
Header Assertions
Checks required headers, content negotiation and security headers.
Cookie Assertions
Validates cookie presence, propagation and session continuity.
Structure Assertions
Ensures objects, arrays and required fields match expected shapes.
Format Assertions
Verifies enums, formats, types and constrained value patterns.
Security Assertions
Validates authentication, authorization signals and sensitive flows.
Capability catalogue
Problems, solutions and outcomes.
Convert Real User Flows Into Automated API Tests
Problem
Creating API automation manually after functional testing is time-consuming and repetitive.
How Flow²Test solves it
Flow²Test records real user flows while testers perform their normal application testing — so you keep testing the way you already do while automation is built in the background.
Outcome
Automatically generated dependency-aware API tests that are ready to execute.
- Continue testing normally
- Automatic API capture
- Dependency-aware generation
- No duplicate effort
OpenAPI Import
Problem
Contracts exist, but turning them into executable suites still takes engineering time.
How Flow²Test solves it
Import OpenAPI from file or URL, configure authentication and generation strategy, preview operations and generate a project.
Outcome
Contract-first teams get a guided path into automation without abandoning review.
Dependency Detection
Problem
Tokens, IDs and path values move between requests and break brittle scripts.
How Flow²Test solves it
Flow²Test analyses responses with JSONPath-based detection and wires variables across the generated sequence.
Outcome
Suites reflect real API flow instead of disconnected request lists.
Authentication Capture
Problem
Login and token exchange are easy to miss when scripting APIs manually.
How Flow²Test solves it
When you test authenticated journeys normally, Flow²Test retains the auth-related conversation for generation and replay.
Outcome
Generated projects start closer to how the application actually authenticates.
Environment Library
Problem
Hard-coded URLs and credentials scatter across frameworks and leak into source.
How Flow²Test solves it
Manage reusable local environments with base URL, headers, auth fields, masking and encrypted local storage.
Outcome
The same automation can move across Dev, QA and UAT without rewriting secrets into code.
REST Assured Generation
Problem
Hand-written Java automation is slow to bootstrap and hard to keep consistent.
How Flow²Test solves it
Generate readable REST Assured Maven projects with JUnit 5 structure from real user flows or OpenAPI.
Outcome
Engineers download projects they own and continue in their IDE — no embedded Studio editor required.
Postman Export
Problem
Some teams still need collections alongside code-based suites.
How Flow²Test solves it
Export a Postman collection as part of generation where supported.
Outcome
Share a familiar artefact without abandoning the generated Java project.
Execution History
Problem
Local runs leave results scattered across IDE consoles and ad-hoc logs.
How Flow²Test solves it
Execute REST Assured locally in Studio and retain project-specific history with status, duration and reports.
Outcome
Teams review outcomes in one place without claiming cloud execution.
Replay Diagnostics
Problem
Failures are hard to attribute — auth, environment drift or broken dependencies can look the same.
How Flow²Test solves it
Inspect replay health, replay quality and diagnostics to spot dependency, auth and environment mismatches.
Outcome
Faster triage without unsupported AI claims.
Coverage
Problem
Pass rate alone does not show whether critical flows and endpoints are exercised.
How Flow²Test solves it
Review overall, endpoint, flow and critical-flow coverage with recommendations and release readiness.
Outcome
Quality conversations move beyond a single green bar.
Release Center
Problem
Stakeholders need evidence, but teams assemble reports manually after each run.
How Flow²Test solves it
Summarise executions and export executive release reports (HTML, PDF, Excel or ZIP where supported).
Outcome
Release evidence without presenting Flow²Test as formal compliance certification.
Git Workspace
Problem
Generated projects become personal folders instead of shared engineering assets.
How Flow²Test solves it
Initialise Git for a Workspace, then branch, commit, push and pull with GitHub, GitLab or a generic remote.
Outcome
Automation follows the same collaboration model as application code. Shared cloud Workspaces remain future scope.
At a glance
Manual API automation vs Flow²Test
| Dimension | Traditional workflow | Flow²Test workflow |
|---|---|---|
| Starting point | Write API requests manually after testing | Continue testing normally — or import OpenAPI — and generate automation |
| Dependencies | Wire tokens and IDs by hand | Detect and generate dependency-aware variables |
| Environments | Credentials in framework files | Reusable local environments with masked secrets |
| Collaboration | Ad-hoc project folders | Git Workspaces and standard branch workflows |
Starting point
Traditional workflow
Write API requests manually after testing
Flow²Test workflow
Continue testing normally — or import OpenAPI — and generate automation
Dependencies
Traditional workflow
Wire tokens and IDs by hand
Flow²Test workflow
Detect and generate dependency-aware variables
Environments
Traditional workflow
Credentials in framework files
Flow²Test workflow
Reusable local environments with masked secrets
Collaboration
Traditional workflow
Ad-hoc project folders
Flow²Test workflow
Git Workspaces and standard branch workflows
Flow²Test accelerates automation while you keep testing the way you already do. Teams still review generated projects and maintain suites as APIs change.
See how to use it next.
Follow the getting-started journey, or return to the product tour if you want another look at Studio.