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 Community
dev.to > whateverneveranywhere > an-http-200-is-not-a-delivered-job-application-nlc

An HTTP 200 is not a delivered job application

6+ hour, 32+ min ago   (336+ words) Every auto-apply tool I have taken apart marks an application "sent" at the same moment: the instant it dispatches the click. That is a read-back of our own input, and it is the weakest signal in the whole pipeline. I…...

DEV Community
dev.to > devyuuun > why-a-pr-walkthrough-can-pass-validation-and-still-be-hard-to-read-3gmb

Why a PR walkthrough can pass validation and still be hard to read

9+ hour, 6+ min ago   (770+ words) I made an HTML guide for reading pull requests. When I shared it with coworkers, the visual feedback was encouraging, but I still felt that parts were hard to follow. One person wanted to see the explanation before the code…...

DEV Community
dev.to > anusha_mukka > stop-returning-access-denied-197b

Stop Returning “Access Denied”

10+ hour, 20+ min ago   (540+ words) Security teams spend a lot of time deciding whether a request should be allowed. The person making that request experiences the decision through a much smaller interface: usually a status code and a sentence. This is Part 3 of Security Infrastructure…...

Implicator.ai
implicator.ai > qwen-claude-three-coding-jobs

Can a Local Coding Model Save You Money?

14+ hour, 48+ min ago   (154+ words) The practical question is whether avoiding a hosted inference charge still looks economical after the machine, electricity, maintenance, review time, and fallback calls enter the calculation. The measurements cover task outcomes, elapsed time, and API charges. The worksheet leaves equipment,…...

Medium
medium.com > @sidhunavjott > your-users-shouldnt-be-your-qa-team-10-website-bugs-ai-can-catch-before-release-e34363d01820

Your Users Shouldn’t Be Your QA Team: 10 Website Bugs AI Can Catch Before Release

6+ hour, 49+ min ago   (33+ words) Modern software moves too fast for manual testing alone. Here’s where AI testing is changing the game. Every …...

DEV Community
dev.to > automate-archit > ai-wont-fix-a-broken-process-map-it-first-then-automate-1jbk

AI Won't Fix a Broken Process. Map It First, Then Automate

11+ hour, 25+ min ago   (1060+ words) Automation copies your process. If the process is confused, you now have confusion running at speed, and nobody to blame in the room because the software did it. That is the failure mode I see most often in businesses between…...

DEV Community
dev.to > emilreiter > reduce-pr-review-time-with-ai-what-the-45-claim-leaves-out-32p4

Reduce PR review time with AI: what the 45% claim leaves out

11+ hour, 25+ min ago   (412+ words) When a team asks how to cut pull request review time with AI, the answer they get is usually a vendor number. Atlassian says Rovo cut PR cycle time by 45% in their dogfooding. That number is real, but it's self-attested:…...

Gearbrain
gearbrain.com > amp > best-usability-testing-companies-services-2677844541

Top 7 Usability Testing Companies

15+ hour, 20+ min ago   (947+ words) A while back, I spent weeks trying to find a usability testing vendor for a product launch. Every call ended with a price that made it easy to put the decision off. A few proposals read like a functional test…...

DEV Community
dev.to > christian-mendes > meu-primeiro-teste-luizalabs-1o8p

meu primeiro teste: LuizaLabs

12+ hour, 7+ min ago   (400+ words) Resolvi voltar a esse projeto agora e documentar aqui a lógica que usei e as decisões que tomei na época, tanto como registro pessoal dessa fase quanto para quem estiver enfrentando um desafio parecido hoje. 🔗 Repositório no GitHub Na época,…...

DEV Community
dev.to > homelabpm > ollamas-responses-api-accepts-previousresponseid-returns-200-and-forgets-the-whole-conversation-1kp8

Ollama's Responses API accepts previous_response_id, returns 200, and forgets the whole conversation

12+ hour, 3+ min ago   (538+ words) Ollama 0.34.0, Debian 13, CPU only, qwen2.5:1.5b. The Responses API, which is the OpenAI-compatible endpoint Codex and similar clients use. Turn 1 plants something the model could not guess: password. Now two controls. The same question with the full history sent in the request…...