Help Center
HOW CAN WE HELP?
Guides, walkthroughs, and references for every stage of your QA workflow.
I want to…
Filters content to your goal
🗂️
All Topics
🚀
Get Started
New to PractiTest
✍️
Build My Test Suite
Tests & requirements
▶️
Run & Track Results
Execution & cycles
⚙️
Admin & Setup
Users & config
🤖
Automate & Integrate
CI/CD & APIs
📊
Report & Analyze
Dashboards & data
Browse by category
✍️ Design your Repository
Intermediate
5 min read
QA EngineerAdmin
How to import tests from Excel or CSV
Use this when migrating existing test cases into PractiTest from a spreadsheet. You can import test fields, steps, BDD scenarios, and linked requirements in one operation.
When to use this
This workflow applies when you are migrating from another test management tool, onboarding a new project with an existing test library, or bulk-creating tests from a specification document.
Before you start: Custom fields you plan to import must exist in your project first. Requirements you want to link must already be in PractiTest.
1Prepare your file
Supported formats: XLSX, Google Sheets, and CSV (UTF-8). The most common structure includes tests and steps in one file.
- The first row of each test contains all test-level info plus the first step
- Additional rows carry only step data for that test
- When a new test begins, repeat all test-level fields in that row
The Name field supports up to 250 characters. If the Author column is empty, the importing user is set as author automatically.
2Open the import tool
- ✓Go to Project SettingsClick the gear icon in the left navigation.
- ✓Navigate to Import & ExportProject Settings → Import & Export → Import Tests
- 3Choose your fileClick Choose File for XLSX/CSV, or Import from Google Drive for a Google Sheet.
- 4Map your columnsType each column header name next to the matching PractiTest field. Required fields are marked with an asterisk.
- 5Click ImportYou'll be redirected to a results page. Each test receives a unique Test ID automatically.
Common mistakes
- Repeating test data in step rows — only the first row of each test should have full test info
- CSV not in UTF-8 — re-save as UTF-8 before importing
- Custom fields not yet created — create them first in Project Settings → Fields
- Author name doesn't match exactly — use exact email or display name as shown in PractiTest
📎 Related tasks
Was this article helpful?
What was the problem? (select all that apply)
Thanks — your feedback helps us improve this article.
Help Center
Troubleshooting
⚠️ Troubleshooting Centre
Something not working?
Find your symptom below. Each guide is structured as: what's happening → why it happens → how to fix it.
Common issues
📥
Import failed or produced errors
File format issues, encoding errors, missing required fields, or custom fields not found.
⚠️
Test results not appearing
Results pushed from CI/CD aren't showing in PractiTest, or run status isn't updating.
🔗
Integration not connecting (Jira, GitHub)
Authentication failures, missing permissions, or webhook not firing.
🔑
Permission or access error
User can't view, edit, or run tests. Role or project membership issue.
📊
Coverage report showing incorrect data
Requirements showing as uncovered despite linked tests, or stale coverage status.
🤖
AI Steps Generator not responding
Generator times out, produces empty steps, or returns an error message.
Can't find your issue?
If your problem isn't listed above, our support team can help. Include your project ID, the steps you took, and any error messages you saw.
Advertisement
Advertisement