# qa-engineering

Published articles for qa-engineering.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## From Bug Report to Production: How I Fix Bugs with AI

DevFeed: [From Bug Report to Production: How I Fix Bugs with AI](<https://devfeed.tech/articles/from-bug-report-to-production-how-i-fix-bugs-with-ai-111025.md>)

Original publisher: [Read original article](<https://hackernoon.com/from-bug-report-to-production-how-i-fix-bugs-with-ai?source=rss>)

Author: inDrive.Tech

Published: 2026-11-01T21:40:15Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [bugfixes](<https://devfeed.tech/topics/bugfixes.md>), [Monitoring](<https://devfeed.tech/topics/monitoring.md>), [Static code analysis](<https://devfeed.tech/topics/static-code-analysis.md>), [engineering-culture](<https://devfeed.tech/topics/engineering-culture.md>), [Risk](<https://devfeed.tech/topics/risk.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [api-testing](<https://devfeed.tech/tags/api-testing.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [claude](<https://devfeed.tech/tags/claude.md>), [clusters](<https://devfeed.tech/tags/clusters.md>), [code](<https://devfeed.tech/tags/code.md>), [code-review](<https://devfeed.tech/tags/code-review.md>), [good-company](<https://devfeed.tech/tags/good-company.md>), [hackernoon-top-story](<https://devfeed.tech/tags/hackernoon-top-story.md>), [indrive](<https://devfeed.tech/tags/indrive.md>), [logs](<https://devfeed.tech/tags/logs.md>), [production](<https://devfeed.tech/tags/production.md>), [production-monitoring](<https://devfeed.tech/tags/production-monitoring.md>), [qa](<https://devfeed.tech/tags/qa.md>), [qa-engineer](<https://devfeed.tech/tags/qa-engineer.md>), [qa-engineering](<https://devfeed.tech/tags/qa-engineering.md>), [quality-assurance](<https://devfeed.tech/tags/quality-assurance.md>), [ship](<https://devfeed.tech/tags/ship.md>), [software-testing](<https://devfeed.tech/tags/software-testing.md>)

### AI overview

The article describes a three-level workflow in which a QA engineer uses Claude to investigate code, verify hypotheses with production logs and metrics, then prepare and ship small fixes through normal review and release checks. Bug reports include a proposed fix, regression criteria, risks, user impact, and code references, with confirmed findings distinguished from hypotheses. Production analysis can reveal misleading error counts: one week of data across 13 clusters showed about 1.86 million 500 errors, roughly 96.6% tied to client cancellations; the proposed handling change was an estimate, not a deployed result. A shipped idempotency-key fix validated requests before reserving keys and released them after failures; duplicate-key errors fell about 30%, with no noticeable response-time or other-error change and an assessed cache load of about 0.01%. The engineer retains responsibility for evidence, scope, tests, review, release, and post-release checks.

### Source excerpt

How a QA engineer at inDrive uses AI to investigate bugs, analyze production logs, write fixes, and ship changes to production.