Locust 2.43.4 Released — What’s New for QA Engineers

What’s New in Locust 2.43.4

Locust version 2.43.4 was released on April 01, 2026.
Here is a summary of what changed and what it means for QA engineers and SDETs.

Official Release Notes

## What's Changed
* adding mqtt user feature that works around the paho mqtt 340 connections limit issue by @ionutab in https://github.com/locustio/locust/pull/3268
* Unset print_stats on workers created by --processes option by @markogle in https://github.com/locustio/locust/pull/3353
* Add Qdrant support by @Anush008 in https://github.com/locustio/locust/pull/3354
* Bump qdrant-client from 1.16.2 to 1.17.0 by @dependabot[bot] in https://github.com/locustio/locust/pull/3362
* Bump sphinxcontrib-htmlhelp from 2.0.1 to 2.1.0 by @dependabot[bot] in https://github.com/locustio/locust/pull/3359
* Bump sphinxcontrib-serializinghtml from 1.1.10 to 2.0.0 by @dependabot[bot] in https://github.com/locustio/locust/pull/3361
* Bump snowballstemmer from 2.2.0 to 3.0.1 by @dependabot[bot] in https://github.com/locustio/locust/pull/3358
* Bump the all_dependencies group with 2 updates by @dependabot[bot] in https://github.com/locustio/locust/pull/3356
* Extract response time bucketing into an overridable function by @thessem in https://github.com/locustio/locust/pull/3373
* Improve Type Hinting for Wait Time Functions by @abstract-333 in https://github.com/locustio/locust/pull/3374
* Bump the eslint group in /locust/webui with 8 updates by @dependabot[bot] in https://github.com/locustio/locust/pull/3363
* Bump the vite group in /locust/webui with 2 updates by @dependabot[bot] in https://github.com/locustio/locust/pull/3364
* Bump typescript from 5.7.2 to 5.9.3 in /locust/webui...

How to Upgrade

# For Python tools
pip install locust --upgrade

# For Node.js tools  
npm install locust@latest

Full release notes: https://github.com/locustio/locust/releases/tag/2.43.4

Here’s a sharp, blog-ready section for your topic — written in your preferred expert + storytelling + SEO style 👇

🚀 PyTest 9.0.3 Released — What’s New for QA Engineers

The latest release of pytest 9.0.3 is not about flashy features — it’s about something more critical:

⚙️ Accuracy, stability, and developer clarity

Let’s break down what actually matters 👇

🔑 Key Improvement 1 — More Accurate pytest.approx Comparisons

What changed:
pytest.approx now correctly respects mapping (dictionary) key order during comparisons. (GitHub)

Why this was needed:
Previously, comparisons involving dictionaries could behave inconsistently — especially in edge cases where order mattered in validation logic.

My expert take:
👉 This fix looks small… but it’s huge for data-heavy testing.

• API response validation
• JSON contract testing
• Financial/data-sensitive assertions

How it helps QA engineers:

• More trustworthy assertions
• Reduced false positives/negatives
• Better confidence in automated validations

🔑 Key Improvement 2 — Clearer Error Handling for Plugin Misuse

What changed:
Trying to disable conftest.py using -p no: now throws a clear UsageError instead of crashing internally. (GitHub)

Why this was needed:
Earlier behavior caused confusing internal assertion failures — hard to debug, especially for teams using custom plugins or shared configs.

My expert take:
👉 This is a developer experience win.

• Turns silent failure → explicit guidance
• Prevents misuse of pytest architecture

How it helps QA engineers:

• Faster debugging
• Cleaner CI/CD logs
• Less time wasted on “WTF is this error?” moments

⚠️ Any Breaking Changes — What You Should Know

Good news:
👉 No major breaking changes in 9.0.3 (it’s a patch release focused on bug fixes).

But… important nuance:

• PyTest 9.x itself is a major version line
• Some older plugins or legacy patterns may already be incompatible

My recommendation:

• If you’re already on 9.x → ✅ safe to upgrade immediately
• If you’re on older versions (7.x/8.x) → ⚠️ test plugin compatibility first

🔄 Migration Notes (Real-World Advice)

Before upgrading:

• ✅ Validate your plugins (pytest-xdist, pytest-asyncio, etc.)
• ✅ Run tests in CI with --maxfail=1 to catch early issues
• ✅ Check custom conftest.py logic (now stricter behavior)

👉 Treat upgrades like pipeline changes, not just dependency bumps

🧠 Final Verdict — Should You Upgrade?

✔ YES — Upgrade if:

• You rely on data comparisons (APIs, JSON, analytics)
• You want cleaner error handling
• You’re already on PyTest 9.x

⏳ WAIT if:

• Your framework depends on legacy plugins
• You haven’t validated compatibility yet

💡 Blog Punchline (Use This 🔥)

“PyTest 9.0.3 doesn’t add features — it removes doubt.
And in testing, confidence is the real feature.”

This article is part of QA Pulse by SK — your weekly signal for QA, Test Automation and AI in Software Engineering. Subscribe free.