Skip to main content

Create Your First Project

Projects in TestFlair are containers for organizing your testing artifacts. Each project holds your requirements, user stories, test cases, test scripts, and linked bugs.

Creating a New Project​

Step 1: Access the Create Project Page​

From the sidebar, click Projects, then click the Create Project button. Alternatively, you can click the create button directly from the dashboard.

Create project button

Step 2: Enter Project Details​

Fill in the project information:

  • Project Name (required) — A descriptive name for your project (e.g., "E-commerce Website Testing")
  • Project Description (optional) — Brief description of what you're testing (max 500 characters)

Project creation form

Step 3: Add Business Requirements​

Choose how to provide your requirements. You can use one or both methods:

  • Upload Files — Upload BRD documents (PDF, DOC/DOCX, RTF, TXT, XLSX, CSV)
  • Add as Text — Type or paste requirements directly
  • Both — Combine file uploads with text input
info

At least one input method is required. You can always add more requirements later from the Project Data tab.

Step 4: Save Your Project​

Click Create Project to save. You'll be taken to your new project where you can start generating user stories.

Project Structure​

Once created, your project is organized into these sections:

SectionDescription
DashboardStatistics and progress for this project
Project DataUpload files and add text context for your requirements
User StoriesAI-generated user stories from your requirements
Test CasesTest cases generated from user stories
Test ScriptsExecutable automation scripts generated from test cases
BugsBugs raised against this project
Test PlansRelease-level planning that groups the testing for a release
Test RunsNamed, rerunnable collections of test cases
API TestsRequest-level tests generated from an OpenAPI spec
SettingsProject details and team member/group assignments
Beta feature

Test Plans, Test Runs and API Tests are Beta features and may not be visible on every account. Contact your workspace admin or [email protected] if you'd like access.

Project tabs

See Projects Overview for more details on navigating your project.

Best Practices​

Naming Conventions​

Use clear, descriptive names:

  • "Customer Portal - User Authentication"
  • "Mobile App v2.0 - Payment Flow"

Avoid vague names like "Project 1" or "Test".

Requirements Quality​

The quality of generated tests depends directly on your requirements:

  • Be specific and detailed
  • Include user flows and edge cases
  • Describe expected behaviors clearly

Next Steps​

With your project created, you're ready to: