Introduction
Welcome to TestFlair — the AI-powered testing platform that transforms your business requirements into comprehensive test coverage.
What is TestFlair?
TestFlair is an intelligent testing platform that automates the entire testing lifecycle. Upload your Business Requirements Document (BRD), and our AI will generate:
- User Stories — Detailed user stories derived from your requirements
- Test Cases — Comprehensive test scenarios, categorized by type (Positive, Negative, Edge)
- Test Data — Realistic input values for your test steps
- Test Scripts — Executable Selenium or Playwright automation
- API Tests — Request-level tests generated from your OpenAPI specification
- Bug Reports — Automatic bug detection and tracking from failed tests
Key Features
AI-Powered Generation
Our AI analyzes your business requirements and generates complete testing artifacts automatically, saving hours of manual work.
Multi-Format Support
Upload requirements in various formats:
- PDF documents (
.pdf) - Word documents (
.doc,.docx) - Rich text (
.rtf) - Plain text files (
.txt) - Spreadsheets (
.xlsx,.csv) - Or add your requirements directly as text
Test Execution & Live Browser Viewing
Execute your generated scripts directly from the platform on integrated Selenium and Playwright infrastructure. Watch the browser live as the test runs, follow real-time logs, and review metrics and history.
Test Runs
Group many test cases into a named, rerunnable set, execute them together, and compare one attempt against the next with per-case results and run analytics. See Test Runs.
API Testing
Import an OpenAPI specification and generate request-level tests from your user stories — variables, assertions and pre/post-request scripting included, with no browser involved. See API Tests.
TestFlair AI
An assistant built into the platform. Describe what you want in plain language and it works against your real projects, asking for your approval before it changes anything. See TestFlair AI.
Work From Your Editor
TestFlair speaks MCP, so the AI assistant in your IDE can drive the whole pipeline — create a project, generate stories, cases and scripts, run them — without switching to the web app. See Connect Your Editor.
Bug Tracking
Automatically create bug reports when tests fail, with screenshots and failure details. Manage your bug lifecycle with detailed status tracking.
Integrations
Connect TestFlair to your existing tools. The Integrations Hub supports two-way Jira sync, Zephyr test-case export, and GitLab/GitHub for pushing bugs to issues and running tests from your CI pipeline.
Dashboard & Analytics
Track testing progress across all your projects with visual statistics, test case status breakdowns, and bug priority overviews.
How It Works
- Create a Project — Set up your testing project with a name and description
- Upload Requirements — Add your BRD files or paste requirements as text
- Generate User Stories — AI creates user stories from your requirements
- Generate Test Cases — Test cases are automatically created from user stories
- Generate Test Scripts — Executable Selenium scripts ready to run
- Execute & Track — Run tests, view real-time results, and track bugs
Getting Started
Ready to start? Follow our step-by-step guide:
- Create an Account — Sign up for TestFlair
- Create Your First Project — Set up your testing project
- Upload Your Requirements — Add your business requirements
- Generate Your First Tests — Run through the full generation flow
Understanding Flairs
Flairs are TestFlair's platform credits. Every AI generation (user stories, test cases, test scripts) consumes Flairs; running tests does not. You can track your Flair balance and per-feature usage in the Settings > Usage section. Free-tier accounts receive a starting Flair allowance, and paid plans include higher limits.
Key Concepts
| Term | Meaning |
|---|---|
| BRD | Business Requirements Document — the input files or text that describe what your application should do |
| Flairs | Platform credits consumed by AI generation |
| User Story | A feature described from an end-user perspective: "As a [user], I want [action] so that [benefit]" |
| Test Case | A set of preconditions, steps, and expected results that verify a feature works correctly |
| Test Script | Executable Selenium or Playwright automation code (Java or Python) generated from a test case |
| Test Run | A named, rerunnable collection of test cases executed as a set |
| API Test | A test that calls your application's endpoints directly, without a browser |
| POM | Page Object Model — a design pattern where page-specific elements are separated into page classes |
| Tunnel | A secure connection (Cloudflare or ngrok) that lets TestFlair's cloud browser reach a locally-running app |
For the full list of terms, see the Glossary.
Need Help?
- Check out our detailed documentation in the sidebar
- See the Troubleshooting guide for common issues
- Contact our support team at [email protected]