Staying on 1.x changes nothing. 2.0 is a breaking upgrade, same Composer package, migration guide planned.
The test format and threshold rules are MIT; the engine is proprietary. github.com/volt-test/contrac…
What would you change in the API?
5/5
10
Typed results from the engine's JSON, down to one step's p99, instead of parsed console text.
And scenario classes you can share across tests. Inline and class scenarios produce the same test definition.
Draft, not released. 4/5
1
6
Checks beyond status: JSON, headers, body, HTML, cookies. Status checks fail the run by default; others only count unless you set onFail.
thresholds() on the test, a scenario or one step. In 2.0, a run with zero responses fails whatever they say.
Draft API. 3/5
1
6
A redesigned API: one fluent builder, a base URL with relative step paths, a typed load builder, json() and bearer() helpers.
Real user flows: seed data once, log in once per virtual user, think time ranges like 1s-3s.
Not released; names can still change.
2/5
1
8
Real users log in once, not before every page. Their pauses vary. And a 200 OK can still carry the wrong data.
VoltTest 2.0 is designed around that. The draft API, one part per image:
1/5
We’re planning V2 of the VoltTest PHP SDK.
The goal isn’t just to add more features.
We want load tests in PHP to feel much closer to describing real user behavior:
setup & teardown
loops and conditions
per-scenario load models
richer assertions
better data handling
more control over HTTP behavior
smoother local → cloud execution
Still designing the API, so this is exactly the right time for feedback.
If you use PHP for performance testing, what would you want in V2?
22
Start locally from your terminal while developing.
When you need more load, run the same test on VoltTest Cloud without provisioning load-generator servers.
Then inspect throughput, success rate, errors, and P50/P95/P99 latency in the dashboard.
1
13
VoltTest lets developers write performance, load, and stress tests in plain PHP.
No YAML. No JavaScript test scripts. No separate toolchain.
Install it through Composer and keep the tests beside your application code:
composer require volt-test/php-sdk --dev
1
30
Something big is brewing.
VoltTest is coming, performance testing, reimagined for developers.
Stay tuned.
How do you know your Laravel app is actually getting faster? We just built the answer. 🔍
Volt-Test Cloud's new Comparison UI takes the guesswork out of optimization.
⚡️ Side-by-side metric deltas (+/- %)
⚡️ Overlaid time-series charts
⚡️ Automated "Fastest Run" winner badges
Stop guessing and start measuring. Secure your spot for Early Access.
volt-test.com
#PHP #Laravel #VoltTest #BuildInPublic
55
"Performance Testing" is not just one command. 🐘
If you're only checking the homepage, you're missing 90% of potential Laravel bottlenecks.
Here are the 7 types of performance tests every PHP/Laravel developer should know. 🧵👇
You don't always need a Scenario Class.
If you want to quickly check how your GET /dashboard handles 100 concurrent users, just run:
php artisan volttest:run your-site.com/specific-url --users=100
1
39
It starts by extending PerformanceTestCase.
You can define a scenario inline (or use an existing class) and run it with the $this->loadTestUrl() helper.
It automatically handles the test server lifecycle for you, or you can enable it in your config.
1
10
This is where Volt-Test shines at handling state.
We use the extracted ${token} to fetch products, grab the ID of the first item found, and pass that ID into the "Add to Cart" step.
It is a real, connected user flow, not just random pinging.
1
39
We define the scenario and feed it unique user data from a CSV (dataSource).
Step 1 hits the registration endpoint. We inject the dynamic data and, crucially, extract the auth token from the response to use later.
1
26
Laravel load testing shouldn't require learning a new tool. 🐘
With Volt-Test, you write complex, stateful scenarios, like a full E-Commerce checkout flow, using the PHP syntax you already know.
100 concurrent users. One Artisan command. Zero context switching. 🧵👇
Laravel devs 👋
API load testing, directly from Laravel ⚡
No test files. Just a URL.
github.com/volt-test/laravel…
1
1
64
Calling all early Volt-Test users!
If you’ve tried Volt-Test to load-test your Laravel or PHP app — I’d love your feedback 💬
What was your favorite part? Anything you’d love to see next?
Your comments help shape the next release. Let’s build Volt-Test together. 💪
#VoltTest #Laravel #PHP #LoadTesting #DevTools
49





















