Frequently Asked Questions

TestifAI is an AI-powered tool that transforms descriptions and screenshots into professional bug reports, feature requests, and improvement tickets. It helps you spend less time writing and more time doing meaningful work.

The generated issues use clear, precise language that avoids ambiguity. Developers get exactly what they need to understand and fix the problem without back-and-forth clarification.

Every team works differently, so TestifAI is fully customizable. Define which sections to include, add project-specific instructions, and save test environments. You shape the output quality while the AI fills in the structure and details. It works with GitHub, GitLab, Linear, Jira, and any other issue tracker.

TestifAI turns detailed issue write-ups into a seconds-long step. Add quick notes, and we generate a complete, ready-to-file ticket for you.

1. Create an account: Sign up with your email address.
2. Create a project: Projects help you organize issues and customize settings.
3. Describe a bug: A brief description is enough. Add a screenshot for even better results.
4. Generate: Click Generate and TestifAI will create a professional issue report.
5. Copy to your tracker: Copy the formatted output to GitHub, Jira, Linear, or any other tool.

Yes, an account is required to use TestifAI. This allows us to save your projects, issue history, and preferences. Your account also enables features like custom issue templates, test environments, and data export.

TestifAI is for anyone who files bug reports, feature requests, or improvements: developers, testers, product managers, and support teams. If you spend more time documenting issues than finding them, or if your reports often need clarification before developers can act, TestifAI can help.

When you submit a bug description, TestifAI uses advanced AI to:

• Analyze your description and any attached images/videos.
• Extract key information (steps to reproduce, expected vs actual behavior).
• Determine issue type (Bug, Feature, Improvement) and priority.
• Generate a structured, professional issue report.

The result is a clear, actionable issue that developers can immediately understand. What used to take several minutes of writing now takes seconds.

For best results, include:

• What happened: Describe the unexpected behavior.
• What you expected: What should have happened instead.
• Steps to reproduce: How to trigger the issue.
• Context: Browser, device, or any relevant details.

Don't worry about formatting or structure. Just describe the problem and TestifAI handles the rest.

Yes! TestifAI supports image and video attachments:

• Images: PNG, JPG, JPEG, GIF, WebP
• Videos: MP4, MOV, AVI, WebM
• Size limit: 100MB per file, 100MB total
• Image analysis limit: 20MB per image, and 40MB across all images in one request

The AI analyzes images to extract relevant information and includes them in the generated issue. That analysis is why images have their own, lower ceiling: an image above 20MB uploads successfully but stops generation, so shrink or crop it first. Videos are never analyzed, so they can use the full 100MB.

TestifAI generates Markdown-formatted issues compatible with:

• GitHub: Issues and Pull Request descriptions.
• GitLab: Issues and Merge Request descriptions.
• Linear: Issues with full Markdown support.
• Jira: Compatible with Jira's Markdown mode.
• Any Markdown-compatible system: Copy and paste works everywhere.

Yes. TestifAI adapts to your workflow, not the other way around. Each project has its own settings, so you can tailor the output for different teams, products, or issue trackers:

• Issue sections: Choose which sections to include (summary, steps, environment, etc.).
• Section order: Drag and drop to reorder sections.
• Custom instructions: Add project-specific guidance for the AI.
• Language: Generate issues in different languages.
• Hide N/A sections: Automatically hide sections that don't apply.

Access these settings from your project's Settings page (click the gear icon or go to Projects → Settings).

Test environments let you save common testing configurations (browser, OS, device type) in your Settings. When generating an issue, you can select one or more environments to automatically include in the report.

You can mark environments as "default" and they will be automatically pre-selected when you create new issues. This saves time and ensures consistent environment details across your bug reports.

You can copy the title and body, then edit them directly in your issue tracker before you file. If you want a different format or more detail, update your input and generate again.

Generated issues are saved in your issue history so you can review, search, and delete them later. Visit the Issues page to manage past drafts.

TestifAI fills in the structure and details so you don't have to. A brief description is enough. The AI extracts information from screenshots, infers steps to reproduce, and generates precise language that developers can act on.

If you want to adjust anything, you can edit the result before copying it to your issue tracker.

ChatGPT is a general-purpose tool. TestifAI is purpose-built for bug reports.

With ChatGPT, you craft prompts, explain the format you want, and copy text between tabs. With TestifAI, you describe the problem once and get a structured issue. Your project settings, custom instructions, and saved environments shape the output automatically. The result is consistent, precise language that developers can act on immediately.

TestifAI may reject input that is:

• Too vague: Not enough detail to create an actionable issue.
• Off-topic: Not a bug report, feature request, or improvement.
• Empty: No meaningful content provided.
• Gibberish: Random or nonsensical text.

Try adding more specific details about what happened, what you expected, and how to reproduce the issue.

A good bug report helps developers understand and fix the issue quickly. Key elements include:

• Clear title: Summarize the issue in one line.
• Steps to reproduce: Exact actions to trigger the bug.
• Expected behavior: What should have happened.
• Actual behavior: What actually happened.
• Environment: Browser, OS, device, app version.
• Screenshots or videos: Visual evidence when applicable.

The challenge is that writing all this takes time. TestifAI generates these sections automatically from a simple description. Try it free.

Common reasons bug reports get ignored:

• Can't reproduce: Missing steps or environment details.
• Too vague: "It doesn't work" without specifics.
• No context: Missing what the user was trying to do.
• Duplicate: Already reported but hard to search.
• Wrong format: Wall of text without structure.

Well-structured reports with clear reproduction steps get fixed faster because developers can immediately start investigating. TestifAI helps you create reports that get action, not ignored.

Aim for comprehensive but concise. Include all necessary details (steps, environment, screenshots) but avoid unnecessary prose. A good bug report is typically 100-300 words with clear sections. The goal is to give developers everything they need without making them read a novel. Bullet points and numbered lists help scannability.

Yes, when relevant. Screenshots and screen recordings are valuable because they:

• Show exactly what you see (eliminates ambiguity).
• Capture error messages verbatim.
• Reveal UI state that's hard to describe.
• Help developers locate the issue faster.

For complex interactions or timing-sensitive bugs, screen recordings are even better than static screenshots.

Mobile bug reports need extra context:

• Device model: iPhone 14 Pro, Samsung Galaxy S23, etc.
• OS version: iOS 17.2, Android 14, etc.
• App version: Usually in Settings → About.
• Network conditions: WiFi, cellular, offline.
• Orientation: Portrait or landscape if relevant.

Screen recordings are especially helpful for mobile since interactions are harder to describe. You can also save your mobile device configurations as test environments in Settings for quick selection.

• Bug: Something is broken. It worked before or doesn't work as documented. Example: "Submit button does nothing when clicked."
• Feature request: Something new that doesn't exist. Example: "Add dark mode support."
• Improvement: Something works but could be better. Example: "Make the loading spinner more visible."

Correctly categorizing helps teams prioritize. Bugs often get higher priority than improvements.

Yes. TestifAI offers a Free plan with 10 issues per 30 days and 1 project. Paid plans add higher limits for teams with more volume. View pricing.

Yes. Pro and Ultra plans are available for higher issue limits and more projects. You can compare plans on the pricing page.

Yes. All paid plans include a 7-day free trial on your first subscription. See details on the pricing page.

Yes. You can upgrade on the pricing page, and manage or cancel from the Billing section in Settings.

Projects help you organize your work. Each project can have its own settings (issue format, language, custom instructions) and maintains a separate history of generated issues. This is useful if you work on multiple products or want different issue formats for different contexts.

Project limits depend on your plan: Free includes 1 project, Pro includes 3 projects, and Ultra includes 100 projects. Each project has independent settings and issue history.

Yes, use the project dropdown in the navigation bar to switch between projects. Your active project determines which settings are used when generating issues and which issue history you see.

Your saved issues live on the Issues page in the main navigation.

Deleting a project permanently removes the project and all its issues. This action cannot be undone. You'll be asked to confirm before deletion.

Use the Forgot password link on the login page to request a reset email. If you need additional help, contact support.

If you're signed in, go to Settings and use the password section to change it. If you're locked out, use the Forgot password flow.

We don't currently support email address changes.

Accounts are temporarily locked after multiple failed login attempts to protect against unauthorized access. The lockout lasts 30 minutes.

If you believe this is an error or need immediate access, contact support.

Yes. You can enable TOTP-based 2FA in Settings. It works with Google Authenticator, Authy, 1Password, and similar apps.

We collect only what's necessary to provide the service:

• Account info: Email, name, password (hashed).
• Usage data: Generated issues, project settings.
• Technical data: IP address, browser info (for security).

We do not sell your data or use it for advertising. See our Privacy Policy for full details.

Bug descriptions and attached files are sent to our AI provider (OpenAI) for processing. This is necessary to generate issues. OpenAI does not use your data to train their models when accessed via API. We do not share your data with any other third parties except as required to operate the service.

Uploads are stored temporarily during issue generation and deleted after processing. For more details, see our Privacy Policy.

Data retention varies by type:

• Account data: Kept until you delete your account.
• Generated issues: Kept until you delete them or your account.
• Uploaded files: Deleted as soon as your issue is generated. Any leftover file is removed automatically once it is more than 24 hours old.
• Sign-in attempt records: Removed once they are more than 24 hours old.

Go to Settings and click "Export Data" in the Privacy & Data section. You'll receive a JSON file containing your personal data, projects, issues and settings, up to 1,000 issues per download. If you have more than that, the app tells you so and you can download again to continue. Exports are limited to a few per hour.

Go to Settings and click "Delete Account" in the Privacy section. You'll need to:

1. Type DELETE MY ACCOUNT to confirm.
2. Enter your current password.
3. Enter your authenticator code, if you have two-factor authentication on.
4. Click Delete Account.

This permanently deletes your account, all projects, and all issues. Some records (like consent logs) are retained for legal compliance.

Yes. We provide data export, account deletion, and transparent data practices as required by GDPR. You can exercise your data rights directly from your Settings or by contacting us.

Passwords are hashed using industry-standard algorithms before storage. We never store plaintext passwords. Even our team cannot see your password.

We implement multiple layers of security:

• Encryption: All data encrypted in transit (HTTPS) and at rest.
• Rate limiting: Protection against brute force attacks.
• Account lockout: Temporary lock after failed login attempts.
• Session security: Secure, HTTP-only cookies.
• Bot protection: Cloudflare Turnstile on sensitive forms.
• 2FA: TOTP-based two-factor authentication.

If you discover a security vulnerability, please report it responsibly by contacting us through the Contact page. Do not disclose vulnerabilities publicly until we've had a chance to address them.

Yes. Uploaded files are:

• Stored temporarily with random, unpredictable URLs.
• Only accessible to you during the session.
• Automatically deleted after issue generation.
• Validated for allowed file types only.

Try these steps:

1. Refresh the page (Ctrl/Cmd + R).
2. Clear your browser cache.
3. Try a different browser.
4. Disable browser extensions temporarily.
5. Check if JavaScript is enabled.

If the problem persists, contact support with details about your browser and the error you see.

Check the following:

• File type: Only images (PNG, JPG, GIF, WebP) and videos (MP4, MOV, AVI, WebM) are allowed.
• File size: Maximum 100MB per file, 100MB total.
• Image size: The AI analyzes images, so each image must be 20MB or smaller and all of them together must be 40MB or smaller. A larger image uploads but stops generation, and several images that are individually fine can still exceed the combined limit.
• Network: Ensure you have a stable internet connection.

If uploads still fail, try a smaller file or different format.

Issue generation typically takes 5-15 seconds. If it's taking longer, the AI service may be experiencing high load. Wait a moment and try again. If the problem persists, contact support.

If you encounter an error, try refreshing the page and attempting the action again. If the problem persists, contact support with details about what you were doing when the error occurred.

Issues are saved per project. Make sure you:

1. Have the correct project selected in the navigation dropdown.
2. Check the Issues page for your active project (click "Issues" in the navigation).
3. Use search or filters if you have many issues.

Use the contact form to reach support, billing, or privacy teams.