Testing & Quality

Unit/integration tests, fuzzing, reliability, and observability for apps.

  • 23 Tracked terms
  • Last 30 days Feed window

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 > debashish_ghosal > 10-sdlc-checks-ai-will-skip-unless-you-make-them-a-gate-581k

10 SDLC Checks AI Will Skip Unless You Make Them a Gate

19+ min ago   (1056+ words) Do you trust AI code? Of course you don't. Not fully. And here is the part that's easy to miss: it usually isn't wrong. It's incomplete. The code compiles, the happy path works, the demo is clean. What's missing is…...


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

42+ 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

50+ 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…...


job-boards.greenhouse.io

Software Engineer in Test SDET

3+ day, 10+ hour ago   (262+ words) The team works on building highly scalable, secure, reliable, enterprise grade SaaS contact center software applications with a Build, Test, Deploy, Maintain, Own mindset, using Microservices based architecture and AWS services. Talkdesk solution supports millions of real time interactions on…...


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

Why agent-browser and Playwright Work So Well Together

1+ hour, 46+ 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, 48+ 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, 59+ 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, 41+ 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)

2+ hour, 21+ 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, 24+ 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…...