Debugging API issues with limited visibility into request and response data wastes time guessing what went wrong - so we added full network inspection to the test tracer.

How It Works

• Full Request and Response Bodies: View complete request payloads and response data for every API call made during test execution, not just headers and status codes, giving you the complete picture of what was sent and received.
• Detailed Headers and Timing: Inspect all HTTP headers, status codes, and precise timing information for each network request, helping you identify performance bottlenecks and configuration issues.
• Comprehensive API Debugging: Filter and search through network calls, examine authentication flows, and troubleshoot failed API integrations directly in the tracer without switching to browser DevTools.

Find network inspection in your test result tracer, where you can expand any network request to see complete request/response details, headers, and timing data for thorough debugging.

Manually updating URLs and configurations when switching between staging and production environments slows down testing workflows—so we added support for multiple environments per application.

How It Works

• Per-Application Environments: Define multiple environments (staging, production, development) for each application in your project, with unique URLs and configurations specific to each environment.
• One-Click Switching: Switch between environments instantly when running tests, eliminating manual URL changes and configuration updates that previously required editing test cases.
• Environment-Specific Configs: Set environment-specific authentication credentials, base URLs, and settings that automatically apply when tests run against that environment.

Configure environments in your project settings under Applications, where you can add staging, production, and custom environments with their own URLs and configurations for seamless testing across your deployment pipeline.

Managing separate QA.tech projects for each application creates overhead and fragments your testing workflow—so we added support for multiple applications within a single project.

How It Works

• Unified Project Management: Configure and manage multiple distinct web applications (frontend, backend, admin panel) from one central project, eliminating the need to switch between separate projects.
• Cross-Application Testing: Create tests that span multiple applications in a single flow, like testing your main app and admin dashboard together, with all results consolidated in one place.
• Simplified Reporting: View test results, metrics, and health status across all your applications in a single dashboard, making it easier to understand your overall quality posture.

Configure multiple applications in your project settings under Applications, where you can add URLs, set base paths, and manage configurations for each application independently.

Catching issues after code is merged to production is too late—so we added automatic testing for preview environments on pull requests.

How It Works

• Automatic Detection: QA.tech detects preview deployments from Vercel, Netlify, and other platforms when you open or update a pull request, eliminating manual URL configuration.
• Pre-Merge Testing: Tests run automatically against your preview environment before code is merged, catching issues early in the development cycle when they're easiest to fix.
• Fast Feedback Loop: Receive instant test results directly on your pull request, enabling reviewers to verify both code quality and functional behavior before approval.

Configure preview environments in your project settings by defining URL patterns and lifecycle rules, then integrate with your GitHub workflow to enable automatic testing on every pull request.

Rerunning entire test suites to catch flaky tests or verify fixes wastes time and resources—so we made the rerun button smarter.

How It Works

• Selective Rerun: The rerun button now intelligently identifies and reruns only the tests that failed in the previous execution, skipping tests that already passed.
• Faster Feedback: Get results on your fixes in minutes instead of waiting for an entire test suite to complete, especially valuable for large test suites with hundreds of tests.
• Cost Efficiency: Save compute resources and testing credits by running only what’s necessary, reducing redundant test execution without sacrificing confidence.

Find the smart rerun button on your test results pages, where it automatically detects failed tests and offers to rerun just those specific cases instead of the full suite.

Generic AI suggestions can miss critical context about your specific application and workflows—so we added a knowledge system that helps the AI understand what makes your project unique.

How It Works

• Upload Documentation and Context: Add links to your documentation, API specs, project requirements, or custom text notes that describe your application's behavior and testing requirements.
• Automatic Knowledge Integration: When chatting or generating tests, the AI automatically searches your knowledge base to provide project-specific suggestions that match your actual requirements.
• Domain-Specific Intelligence: Set global context rules that apply to all tests, like data formats, authentication flows, or quality standards unique to your application.

Find knowledge management in your project settings, where you can add documentation URLs, custom context, and project-specific guidelines that improve AI accuracy across all test creation.

As test suites grow, finding and managing related tests becomes increasingly difficult—so we added hierarchical organization to help you structure tests logically.

How It Works

• Nested Scenario Structure: Create parent and child scenarios to organize tests hierarchically, like “User Authentication” > “Login Flow” > “Forgot Password”, making complex test suites easier to navigate.
• Clearer Test Planning: Group related test cases under common scenarios, reflecting your application’s structure and user journeys, so your test organization matches how you think about your product.
• Easier Maintenance: Quickly locate and update related tests by browsing the hierarchy, reducing time spent searching through flat lists of test cases.

Find scenario management in your project’s test cases section, where you can create, nest, and organize scenarios to match your testing strategy.

Explaining complex bugs or design requirements through text alone can be time-consuming and prone to misunderstanding—so we added support for visual attachments in chat.

How It Works

• Upload Screenshots and Mockups: Attach images directly to your chat messages to show the AI exactly what you're seeing, whether it's a bug, a design mockup, or expected behavior.
• Share Documentation as PDFs: Upload PDF documents containing specs, requirements, or reference materials that the AI can read and use to create more accurate tests.
• Visual Bug Reporting: Describe issues faster by combining screenshots with text explanations, helping the AI understand visual bugs and UI discrepancies immediately.

Find the attachment button in the chat composer to start adding images and PDFs to your conversations. Supported formats include PNG, JPG, and PDF files.

Creating and managing tests often means navigating through multiple screens and remembering where everything is—so we built a conversational interface that lets you work naturally.

How It Works

• Natural Language Test Creation: Describe what you want to test in plain English, and the AI assistant generates complete test cases based on your requirements—no clicking through forms or menus.
• Project Context Awareness: The assistant knows your project inside and out, drawing from your existing tests, application knowledge graph, and documentation to provide relevant suggestions.
• Conversational Workflow: Ask follow-up questions, refine tests iteratively, run tests in the background, and get help—all through a natural back-and-forth conversation.

Access the chat assistant from your project dashboard to start creating tests conversationally. The assistant automatically uses 20+ specialized tools to help you accomplish your testing goals.

Managing multiple projects over time can lead to a cluttered workspace—so we added a simple way to keep things organized without losing your history.

How It Works

• Archive Inactive Projects: Easily archive projects you're no longer actively using, removing them from your main project list while preserving all historical data and test results.
• Cleaner Workspace: Focus on what matters by keeping only active projects visible, making it easier to find and navigate to the projects you're currently working on.
• Restore When Needed: Archived projects remain accessible and can be restored at any time if you need to revisit them or bring them back into active use.

Project archiving is available in your organization settings, giving you complete control over your workspace organization.