Collection

QA and production readiness

Testing, audits, maintenance and hardening practices for reliable production software.

Blog posts
35
Topic
Delivery and QA

Start here

Latest in this collection

One Git change branches into two paths, retry.go and retry_test.go Delivery & QA

Alibaba Open Code Review returned no comments. Which files did it check?

One invoice, two retry keys. See why Alibaba’s CLI selected the code but skipped the test that changed the payment contract.

A water meter dial with a regular reading and a separate leak alert Delivery & QA

How can a water utility field-test a LoRaWAN meter reading and leak alarm?

A water meter can deliver a reading while its leak alarm is still untested. What to ask a supplier to show at two sites before placing a larger order.

Two delivery paths meet at one checked acceptance point Delivery & QA

Both software vendors say they’re done. What should you test before signing off?

A customer paid and the operator had no order. Follow one transaction across two systems and decide what evidence is worth asking for before release.

Shield marking an AI tool installation review across a README, archive and installed files Delivery & QA

README ZIP malware: review the actual AI tool install

A clean SKILL.md cannot cover every installation input. Compare six harmless change scenarios and see when a previous review needs another decision.

Document lines and a circular mark framed by two brackets Delivery & QA

AI-generated Odoo modules: audit the business contract

An approval flag can hide unauthorized or stale decisions. Follow a disclosed code specimen through thirteen failed-versus-corrected contract cases and separate native Odoo release gates.

A circular review loop connects source, target and review markers Delivery & QA

Odoo migration acceptance: reconcile records and balances

Matching counts and totals can hide wrong orders. Reproduce nine local comparison cases and adapt a proposed CSV that separates test evidence from business approval.

Complete article directory

  1. Alibaba Open Code Review returned no comments. Which files did it check?
  2. How can a water utility field-test a LoRaWAN meter reading and leak alarm?
  3. Both software vendors say they’re done. What should you test before signing off?
  4. README ZIP malware: review the actual AI tool install
  5. AI-generated Odoo modules: audit the business contract
  6. Odoo migration acceptance: reconcile records and balances
  7. Odoo AI agent tests: validate saved activities
  8. Odoo 20 permissions migration: test company isolation
  9. Odoo 19 to 20 AI: what must you reaccept?
  10. Odoo AI import mapping: validate supplier prices
  11. Odoo BMD export: reconcile the batch before monthly handoff
  12. Lovable Data Exposure: How to Prove a Permissions Fix
  13. Google’s Elephant-Goldfish Model: Review the Plan Before Code
  14. LangSmith Trace Retention: Sampling, Evals and Cost
  15. Software Agencies Austria: A 2027 Development and QA Guide
  16. Ultramarine 1 Flash for document agents: pricing, API limits and a migration test
  17. Greptile Base vs Plus vs Apex: A PR Review Budget
  18. Arga Labs vs Archal: Stateful Agent Integration Tests
  19. Canary AI QA: Test Defect Detection, Not Benchmark Scores
  20. Cua for Desktop QA: A Browser-to-Native Test Protocol
  21. Browser Use vs Playwright: Verify Authenticated Actions After Timeouts
  22. ChatGPT Dots + GitHub: From Bug Report to Reviewed PR
  23. Agentic Testing vs Test Automation: 2026 Pilot Guide
  24. OpenAI Eval Sandbox Escape: 12 Controls Before You Test a Cyber Agent
  25. Cisco Antares Review: 1B Local AI for Vulnerability Localization
  26. External QA Benchmark: What We Find in the First 30 Days
  27. What Software Maintenance Costs After Launch: A DACH SaaS Benchmark
  28. Agile De-engineering
  29. Lovable, Bolt, and Replit App Due Diligence
  30. The Vibe-Code Production-Readiness Checklist
  31. What It Costs to Make a Vibe-Coded App Production-Ready
  32. QA for AI-Generated Code
  33. From Lovable and Cursor Prototype to Production: The Migration Checklist
  34. Vibe-Coded Software Audit: What to Check Before Launch
  35. What Test-Driven Development Can and Cannot Prove
Inbox, without the noise

Get the next Delivery and QA field note

One concise email when we publish. No tracking pixels, and no inbox filler.