Reviewing pull requests without understanding their real-world behavior means issues slip through even when code looks correct—so we added automatic exploratory testing that runs on every PR.

How It Works

• Auto-Triggered Exploration: When you open or update a pull request, QA.tech automatically runs exploratory tests against the preview environment, discovering how your changes actually behave in practice.
• Unexpected Issue Detection: The AI explores your PR changes autonomously, identifying edge cases, UI issues, and unexpected behaviors that code review alone would miss, all before merging.
• PR Comment Reports: Get comprehensive exploration reports posted directly as PR comments, showing discovered issues, tested flows, and recommended actions for reviewers to consider.

Enable PR exploratory testing in your GitHub integration settings, and every pull request will automatically receive an AI-powered exploration report highlighting potential issues before code reaches production.

Understanding project health and test performance from fragmented views makes it difficult to spot trends and take action quickly—so we redesigned the project dashboard with improved metrics and navigation.

How It Works

• At-a-Glance Health Overview: See your project’s test success rates, recent run history, and key health indicators on a redesigned dashboard that surfaces the most important information first.
• Trend Visualization: Track test performance over time with visual trends showing pass/fail rates, execution times, and stability metrics, helping you identify patterns and regressions quickly.
• Streamlined Navigation: Access tests, results, settings, and analytics more efficiently with improved layout and information architecture that reduces clicks and cognitive load.

The new dashboard is now your default view when accessing any project, providing immediate visibility into test health and quick access to the most common workflows for managing and analyzing your tests.

Manually exploring applications to find edge cases and unexpected behaviors takes significant time and often misses issues—so we added autonomous exploratory testing directly in chat.

How It Works

• Autonomous Exploration: Ask the chat assistant to explore your application, and it autonomously navigates through features, tests user flows, and discovers potential issues without requiring manual test case creation.
• Intelligent Issue Discovery: The AI identifies edge cases, UI inconsistencies, and unexpected behaviors during exploration, providing detailed reports of what it found and why it might be problematic.
• Automatic Test Suggestions: After exploration, get AI-generated test case suggestions based on discovered flows and issues, helping you quickly convert exploratory findings into permanent regression tests.

Start exploratory testing from the chat assistant by asking it to explore your application or specific features, and receive comprehensive exploration reports with suggested tests and discovered issues.

Testing internal applications typically requires exposing them to the internet or setting up complex VPN configurations—so we added SSH proxy tunnel support for secure, direct access to applications behind firewalls.

How It Works

• SSH Tunnel Configuration: Set up secure SSH proxy tunnels in your project settings, allowing QA.tech to access internal applications without exposing them to the public internet or requiring VPN infrastructure.
• Enterprise-Friendly Security: Test staging environments, internal tools, and applications behind corporate firewalls using industry-standard SSH tunneling, maintaining your security posture and compliance requirements.
• Simple Setup: Configure tunnel endpoints once in your project settings, then run tests against internal applications as easily as testing public sites, with automatic connection management handled by QA.tech.

Configure SSH proxy tunnels in your project settings under Network, where you can add tunnel endpoints with authentication credentials to enable secure testing of internal applications.

Manually creating tests through the UI doesn't scale for teams that want to automate test generation from their own tools and workflows—so we built a comprehensive API for programmatic test management.

How It Works

• RESTful Test Creation: Create new test cases programmatically via API with full control over test names, goals, dependencies, and configurations, enabling integration with your existing development workflows.
• CI/CD Integration: Automatically generate tests from your continuous integration pipelines, ticketing systems, or custom scripts, making test creation part of your automated development process.
• Flexible Authentication: Secure API access using project-specific tokens with Bearer authentication, allowing you to safely integrate QA.tech into your automated systems and tools.

Access the API documentation in your project settings to get started with programmatic test creation, including complete request examples, authentication guides, and integration patterns for common CI/CD platforms.

Understanding testing costs and usage patterns without detailed metrics makes budget planning difficult—so we added comprehensive billing and usage visibility.

How It Works

• Detailed Usage Metrics: View complete breakdowns of test runs, compute minutes, and resource consumption by project and time period, giving you clear visibility into where testing resources are being used.
• Cost Transparency: See actual costs associated with your testing activity, with historical trends and comparisons to help you understand spending patterns and plan budgets effectively.
• Project-Level Insights: Drill down into usage by individual projects to identify high-cost areas, optimize test efficiency, and make informed decisions about resource allocation.

Access billing metrics in your organization settings under Billing, where you can review usage history, analyze spending trends, and export detailed reports for financial planning and cost optimization.

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.