# VoltTest
> Performance, load, and stress testing platform for PHP and Laravel developers. Powered by a Go engine scaling to 10M+ virtual users.
> Full reference: https://volt-test.com/llms-full.txt

## Main Pages
- [Home](https://volt-test.com): Landing page with product overview
- [Features](https://volt-test.com/features): Platform capabilities — Go engine, PHP SDK, Laravel integration, real-time metrics, cloud testing
- [Pricing](https://volt-test.com/pricing): Free and paid plans for load testing (Free $0, paid plans available)
- [About](https://volt-test.com/about): Founder Islam A-Elwafa's story of the production outage that led to VoltTest, a PHP-native load testing platform
- [Documentation](https://docs.volt-test.com): PHP SDK and Laravel package guides
- [Laravel Package Docs](https://docs.volt-test.com/docs/laravel/laravel-installation): Laravel integration setup and usage

## Solutions
- [Solutions](https://volt-test.com/solutions): Use-case guides for load testing PHP APIs, Laravel applications, and e-commerce flows
- [PHP API Load Testing](https://volt-test.com/solutions/php-api-testing): Load testing REST and JSON APIs built in PHP — chained authenticated requests, token extraction from JSON responses, CSV-driven virtual users, and p95/p99 latency reporting
- [Laravel Load Testing](https://volt-test.com/solutions/laravel-load-testing): The Laravel package — two Artisan commands, test scaffolding from your real route table, per-virtual-user session handling, and PHPUnit assertions that fail a build on a p95 regression
- [E-commerce Load Testing](https://volt-test.com/solutions/ecommerce-load-testing): Rehearsing a sale spike — staged load profiles, weighted browse-and-buy funnels, a real cart per shopper, and why a 4xx counts as a successful request unless you assert on the status

## Comparisons
- [Compare VoltTest](https://volt-test.com/compare): Side-by-side comparisons with popular load testing tools
- [VoltTest vs k6](https://volt-test.com/compare/volttest-vs-k6): PHP-native alternative to k6 — write tests in PHP instead of JavaScript, with managed cloud and native Laravel integration
- [VoltTest vs JMeter](https://volt-test.com/compare/volttest-vs-jmeter): Modern cloud-native alternative to JMeter for PHP teams — Go engine vs Java GUI, managed infrastructure vs self-hosted
- [VoltTest vs LoadForge](https://volt-test.com/compare/volttest-vs-loadforge): LoadForge alternative for Laravel teams — PHP tests versioned in your repo vs Locust scripts in Python, plus local execution vs a hosted-only platform

## Glossary
- [Load Testing Glossary](https://volt-test.com/glossary): Definitions of 20 load, stress, and performance testing terms, each on its own page
- [Assertion](https://volt-test.com/glossary/assertion): An assertion is a check applied to a response during a load test — on status, body, or headers — that decides whether a request genuinely succeeded.
- [Breakpoint Test](https://volt-test.com/glossary/breakpoint-test): A breakpoint test ramps load steadily upward until the system violates its targets or fails, in order to find the exact load at which capacity runs out.
- [Concurrent Users](https://volt-test.com/glossary/concurrent-users): Concurrent users are the users active in a system at the same moment — in a load test, the virtual users holding an open session or an in-flight request.
- [Connection Pool](https://volt-test.com/glossary/connection-pool): A connection pool is a fixed set of reusable open connections to a database or upstream service, shared between an application’s concurrent requests.
- [Error Rate](https://volt-test.com/glossary/error-rate): Error rate is the share of requests in a test that failed — connection errors, timeouts, unexpected status codes, or responses that failed an assertion.
- [Latency](https://volt-test.com/glossary/latency): Latency is the delay before a transfer begins — the time to get a request to the server and the first byte of the answer back, excluding transfer time.
- [Load Profile](https://volt-test.com/glossary/load-profile): A load profile is the shape of load over time in a test — how many virtual users are active at each moment, from ramp-up through steady state to ramp-down.
- [P95 / P99 Percentiles](https://volt-test.com/glossary/percentiles-p95-p99): A P95 of 800 ms means 95% of requests finished within 800 ms. P99 says the same at 99% — both describe the slow tail that an average conceals.
- [Ramp-Up](https://volt-test.com/glossary/ramp-up): Ramp-up is the period over which a test climbs from zero to its target load, adding virtual users gradually instead of starting all of them at once.
- [Requests Per Second (RPS)](https://volt-test.com/glossary/requests-per-second): Requests per second is the number of HTTP requests a system handles each second — the most common concrete unit for expressing load test throughput.
- [Response Time](https://volt-test.com/glossary/response-time): Response time is the total elapsed time from sending a request to receiving the complete response — everything the client waits for, network included.
- [Saturation Point](https://volt-test.com/glossary/saturation-point): The saturation point is the load at which throughput stops rising even as more users arrive — the moment a resource runs out and queueing takes over.
- [Scenario](https://volt-test.com/glossary/scenario): A scenario is one complete user journey in a load test — an ordered sequence of steps that a virtual user executes from beginning to end.
- [Soak Test](https://volt-test.com/glossary/soak-test): A soak test holds a moderate, realistic load for hours or days to surface problems that only appear over time, such as memory leaks and pool exhaustion.
- [Spike Test](https://volt-test.com/glossary/spike-test): A spike test applies a sudden, extreme jump in load and then removes it, to see whether a system absorbs the surge, sheds it cleanly, or falls over.
- [Stress Test](https://volt-test.com/glossary/stress-test): A stress test pushes a system beyond its expected peak load to find where it degrades, what breaks first, and whether it recovers once the load drops.
- [Think Time](https://volt-test.com/glossary/think-time): Think time is the pause a virtual user takes between steps to imitate a real person reading, typing, or deciding before making the next request.
- [Thread Group](https://volt-test.com/glossary/thread-group): A thread group is JMeter’s unit of load: a named pool of threads that each run the same request sequence, with its own user count, ramp-up, and loop count.
- [Throughput](https://volt-test.com/glossary/throughput): Throughput is the rate of work a system completes over time — usually requests, transactions, or bytes per second, measured at the completing end.
- [Virtual Users (VUs)](https://volt-test.com/glossary/virtual-users): A virtual user is a simulated client that runs a test scenario end to end, independently and in parallel with every other virtual user in a test.

## Blog
- [How to Load Test Laravel Applications: Tools, Setup, and Real Results](https://volt-test.com/blog/laravel-load-testing): Learn how to load test Laravel apps with PHP-native tools. Step-by-step setup with VoltTest, CSRF handling, auth flows, CI/CD automation, and real results.
- [PHP Load Testing: How to Load Test PHP Applications](https://volt-test.com/blog/php-load-testing): A practical guide to load testing PHP applications — why it matters, what tools are available, and how to write your first PHP load test with VoltTest.
- [VoltTest Cloud Closed Beta Is Now Open: How to Get Access](https://volt-test.com/blog/volt-test-cloud-closed-beta-open): VoltTest Cloud is opening its closed beta. Learn what's included, how the waitlist and invite process works, and how to run your first cloud load test from the PHP SDK or Laravel in minutes.
- [PHP Stress Testing Tool: How to Stress Test PHP & Laravel Apps](https://volt-test.com/blog/php-stress-testing-tool): A practical guide to stress testing PHP applications — what to look for in a PHP stress test tool, how the top tools compare, and how to run your first stress test on plain PHP or Laravel in minutes with VoltTest.
- [Load Testing Laravel Applications with PHPUnit and VoltTest](https://volt-test.com/blog/laravel-load-testing-with-phpunit): Learn how to run realistic performance and load tests in your Laravel application using PHPUnit and VoltTest — no extra scripts, no new syntax.
- [Effortless Laravel Performance Testing with VoltTest PHP SDK](https://volt-test.com/blog/effortless-laravel-performance-testing-with-volt-test-php-sdk): Discover how to seamlessly integrate VoltTest PHP SDK into your Laravel applications for efficient performance testing. Learn to create, run, and analyze tests with ease.
- [Performance Testing: Types and Differences with Examples](https://volt-test.com/blog/performance-testing-types): Learn about different types of performance testing with examples and differences between them. By understanding these types, you can choose the right tests to conduct based on your application's requirements.
- [Stress Testing Laravel Applications with VoltTest (Web UI Flow)](https://volt-test.com/blog/stress-testing-laravel-with-volt-test-web-ui): This tutorial walks you through setting up and executing stress tests on a Laravel application using the VoltTest PHP SDK. You will learn how to simulate real user interactions such as visiting the home page, registering a new user, and accessing the dashboard, ensuring your application can handle concurrent traffic efficiently.
- [Introducing VoltTest: Stress & Load Testing for PHP Developers](https://volt-test.com/blog/introducing-volt-test-php-load-testing): Introducing the VoltTest PHP SDK — a load testing tool that lets PHP developers write performance tests in native PHP, powered by a Go engine.

## Key Facts
- Go engine delivers 275 req/s per virtual user
- Scales from 1,000 to 10,000,000+ concurrent virtual users
- Under 50 MB memory per 1,000 VUs
- Native PHP SDK installed via Composer: composer require volt-test/php-sdk --dev
- Laravel package with Artisan commands (volttest:make, volttest:run) and automatic route discovery
- Real-time metrics dashboard with P50/P95/P99 latency percentiles
- Automatic error classification and request-level sampling
- Distributed cloud testing across multiple regions
- Free tier: 500 VUs, 10 minute tests

## How It Works
1. Install: Add the PHP SDK via Composer (composer require volt-test/php-sdk --dev) or the Laravel package
2. Define: Write test scenarios using a fluent PHP API — set virtual users, define steps, validate responses
3. Run: Execute locally with `php test.php` or `php artisan volttest:run`, or add `--cloud` for distributed testing