Testing & Quality

Unit, integration, E2E, contract tests, test data, coverage, and performance/chaos testing.

  • 4 Subtopics
  • 5 Tracked terms
  • Last 30 days Feed window

Inside Testing & Quality

What this topic collects on

An article joins this feed when it matches these terms. Each one is also a search of its own.

Latest in Testing & Quality


dev.to > valenciamoss6824 > nodejs-sending-domain-onboarding-one-bundle-setup-staged-mail-verification-for-cutover-382c

Node.js Sending Domain Onboarding: One Bundle Setup, Staged Mail Verification for Cutover

20+ min ago   (571+ words) For an e-commerce sending domain, a one-step onboarding bundle can simplify setup, but it cannot make DNS and mail verification happen at one instant. A hostname cutover is complete only when deliverability evidence comes from the records that recursive resolvers…...


dev.to > xtsoftwarelabs > testing-rust-code-without-adding-test-only-traits-1h2f

Testing Rust Code Without Adding Test-Only Traits

28+ min ago   (623+ words) A common pattern in Rust unit tests looks like this: You have a small function that calls the filesystem, a clock, a socket, an FFI function, or some other dependency. The production code is simple. Then you try to unit…...


dev.to > gyu07 > why-agent-browser-and-playwright-work-so-well-together-17c0

Why agent-browser and Playwright Work So Well Together

1+ hour, 24+ min ago   (1478+ words) We recently added agent-browser to our UI evaluation workflow. The motivation was simple. A normal E2E test is great when we already know the path: But sometimes I want to ask a different question: I don't necessarily care which valid route…...


dev.to > hackjs_8688 > when-the-free-tier-stops-being-cheap-a-load-based-exit-test-for-agent-backends-2bfh

When the Free Tier Stops Being Cheap: A Load-Based Exit Test for Agent Backends

1+ hour, 26+ min ago   (456+ words) A team moves its nightly agent job onto a free endpoint. Week one looks perfect. Week four, the queue drains ten minutes late and the on-call engineer has no data. The endpoint did not break. The workload changed shape around…...


dev.to > megapixel99 > the-working-set-that-never-saturated-5fl3

The Working Set That Never Saturated

1+ hour, 37+ min ago   (679+ words) Every experiment in this series had charged each byte of a count table as resident memory. That is a real assumption and nobody had examined it, which I noticed only after reading someone else's project: a third-party runtime that runs…...


dev.to > tessainsley > comparing-ai-review-tools-what-the-numbers-actually-tell-you-3dh2

Comparing AI review tools: what the numbers actually tell you

2+ hour, 19+ min ago   (1485+ words) Most "best AI code review tool" comparisons start and end with a benchmark score. That score hides almost everything a team needs to decide with. The useful move is to read the method behind the number, because the number only…...


dev.to > edgestorage > a-review-checklist-for-ai-coding-agent-output-7-things-i-check-before-trusting-a-change-276c

A review checklist for AI coding agent output (7 things I check before trusting a change)

1+ hour, 59+ min ago   (496+ words) Every team running an AI coding agent eventually hits the same wall: the agent produces a lot of output, and reviewing that output is now the bottleneck. A terminal transcript is not a review artifact. Here is the checklist I…...


dev.to > hackrs_6393 > make-each-characterization-test-fail-once-before-you-refactor-47ka

Make Each Characterization Test Fail Once Before You Refactor

2+ hour, 1+ min ago   (641+ words) A characterization test that cannot fail is decoration, not a safety net. Most messy-repo refactors fail the same way. You record golden values, they all pass, and you feel safe. Then you extract a function and ship a silent behavior…...


dev.to > cole_halton_42f71d71b809b > why-you-shouldnt-let-the-model-review-its-own-ai-code-1llg

Why you shouldn't let the model review its own AI code

4+ hour, 21+ min ago   (258+ words) Krentsel, Agarwal, Cemri, Zaharia and Stoica just put a paper up on arXiv called "Reality Is the Final Verifier: On Two Key Gaps in Agentic Software Engineering" (2609.12039). It's the clearest statement I've seen of why the whole "let the AI…...


indiasnews.net > news > 27/93/06016 > from-traditional-qa-to-ai-led-quality-engineering-the-yogiti-story

From Traditional QA to AI-Led Quality Engineering: The Yogiti Story

10+ hour, 24+ min ago   (287+ words) ANI 14 Sep 2026, 23:34 GMT+ New Delhi [India], September 14: Every enterprise now wants AI in its delivery pipeline. Far fewer have worked out what that actually changes about how software gets tested, released and kept running. Yogiti Technologies has spent the last…...