Our custom GPT reformats your existing test cases into Testpad's format in about five minutes – no manual copying, no tedious restructuring.
By Pheobe
March 25, 2026
Share this article
etting your test cases into Testpad is simple, but if you've exported them from a different tool or spreadsheet, they might need a little reformatting first. Our custom GPT handles that in about five minutes – just paste your tests in, review the output, and import.
Here's what you do:
The custom GPT handles the formatting grunt work. You just check it makes sense and adjust anything that doesn't.
The custom GPT handles formatting. You handle making sure the tests are actually useful for your product.
The custom GPT takes your existing tests and converts them into Testpad's outline structure.
Your spreadsheet might have:
| Test ID | Feature | Steps | Expected result | Priority |
|---|---|---|---|---|
| TC–001 | Login | 1. Navigate to login page 2. Enter valid credentials 3. Click submit | User successfully logs in | High |
Here's one example, though the output will vary depending on your input and what you ask for:
Login
Valid credentials log user in successfully
Invalid password shows error message
Locked account displays warning
By default, it focuses on what to check – stripping out metadata like test IDs, dates, and priorities. If you want to keep any of that, just ask.
The custom GPT gets you about 90% there, but you still need to:
Cut irrelevant tests – It converts everything from your spreadsheet. Remove tests that don't apply to your current testing needs.
Add missing details – Your old tests might not cover edge cases you've discovered since. Add them now.
Adjust prompt style – The GPT creates brief, exploratory-style prompts. Make them more or less detailed based on who's testing.
Check grouping – Sometimes the logical structure doesn't match how you test. Reorder to match your workflow.
This takes about five minutes per script. Compare that to manually reformatting tests (20–40 minutes per script).
Testpad reads indented text and converts it automatically. When you paste the custom GPT's output:
The custom GPT already knows this format, so the output pastes cleanly.
The custom GPT takes its cue from your input. If your existing tests look like formal test cases – preconditions, steps, expected results, metadata – the output will reflect that structure, just converted into Testpad's lighter outline format.
If you'd rather end up with shorter, exploratory-style prompts, you need to ask for that specifically. Something like "convert these to brief Testpad prompts and strip the formal structure" works well.
Don't assume it'll simplify everything by default. Give it direction and it'll follow.
Yes. The custom GPT handles:
Just copy what you have and let the GPT figure it out. If it doesn't do exactly what you wanted, add a few instructions and try again.
The custom GPT preserves logical grouping while simplifying format. If your tests are organized by feature → user story → test cases, that structure survives the conversion.
Your tool has test cases organized as:
Feature: User Profile
Story: Update Email Address
TC–100: Valid email format accepted
TC–101: Invalid email format rejected
TC–102: Duplicate email shows error
Story: Change Password
TC–200: Strong password accepted
TC–201: Weak password rejected
Custom GPT converts to:
User Profile
Update email address
Valid email format accepted
Invalid email format rejected
Duplicate email shows error
Change password
Strong password accepted
Weak password rejected
Same logical structure, just cleaner.
Yes, but free accounts work fine. The custom GPT is available here once you're logged in.
If you've got a paid ChatGPT account, it'll process faster and handle longer inputs, but the free tier handles typical test script imports without issues.
You can use regular ChatGPT, Claude, or any AI tool, but you'll need to explain Testpad's format every time.
With the custom GPT: "Convert these to Testpad format" + paste your tests
With generic AI: "Convert these test cases to an outline format suitable for Testpad. Use indentation to show hierarchy, with top-level sections unindented, subsections indented with 2–4 spaces, and individual test prompts marked with '-'. Keep prompts brief and exploratory rather than detailed step-by-step instructions. Here are my tests: [paste]"
The custom GPT saves you from repeating those instructions each time.
Bear in mind you may need a few rounds of back-and-forth to get the formatting right – generic AI tools can be unpredictable around spacing, bullets, and blank lines.
Two things usually cause issues: the formatting of the output, or how the GPT interpreted your input.
If it's a formatting problem, check that:
If the structure or content isn't what you wanted – wrong grouping, wrong level of detail, tests that miss the point – paste the problem section back into the custom GPT and give it more specific instructions. That usually sorts it.
Migration is a good moment to think about what you actually use. Tests for deprecated features, scripts no one ever runs, duplicates that built up over years – none of that needs to follow you into a new tool.
Bring forward what's useful and leave the rest behind.
If you're reading about importing test cases to a tool you don't have yet, maybe try us? Start your free 30-day trial – no credit card needed.
If you liked this article, consider sharing
EDITORIALS
You know testing your product is essential, but as you dive into the research on how to write a test plan, it feels overwhelming—too formal, too complicated, and filled with more considerations than you know what to do with. What if we told you it doesn’t have to be that hard?
EDITORIALS
Using ChatGPT can help you generate test ideas faster and more efficiently. We'll show you how Testpad's checklist format makes it easy to turn those AI-generated ideas into action.
EDITORIALS
Writing test scripts can be straightforward, but the industry's jargon can make it seem overwhelming. Learn what test scripts are, why they're important, and how to start writing them.