198
0
DiscussionTrending
How we cut CI from 45 minutes to 8 minutes — a practical breakdownSix months ago our test pipeline blocked PRs for 45 minutes. Today it's 8 minutes. Here's every change we made, in…
5.2k views1980
7 discussions
142
0
DiscussionTrending
What we learned from load testing our own API with k6 — things nobody warns you aboutWe ran our first real k6 load test last quarter targeting 500 concurrent users. A few things that surprised us: The…
3.9k views142
79
0
Q&ATrending
How do you parallelise 1000+ tests to run in under 10 minutes in CI?Our test suite: 1200 Playwright tests, currently runs serially in ~55 minutes. Target: under 10 minutes for the PR…
2.1k views79
74
0
Q&ATrending
k6 vs JMeter vs Gatling in 2026 — which would you choose for a new project?Starting a new performance testing initiative. Our stack: Node.js microservices, REST APIs, ~50k requests/day in…
2.0k views74
42
0
Q&ATrending
How do you write meaningful performance assertions in your load tests?Most load test examples I see just report numbers (p95, p99, RPS) without failing the test definitively. I want our…
1.2k views42
27
0
Q&ATrending
How do you integrate performance tests into CI without bloating build time?We want to add k6 performance tests to our CI pipeline but our PR pipeline is already 12 minutes and I don't want to…
834 views27
0
0
PollTrending
Has your team shifted performance testing left (earlier in the dev cycle)?0 votes · select an option to vote
2.0k views0