---
title: "srinath (@srinathy) | Hashnode"
description: "Building Hawzu. Writing about software quality, uncertainty, and the future of test management. Read the latest articles by srinath on Hashnode."
url: "https://hashnode.com/@srinathy"
---

@srinathy

# srinath

@srinathy · Joined July 2026

Building Hawzu. Writing about software quality, uncertainty, and the future of test management.

### [Why a Finished Run Refuses Your Edits](https://hawzu.hashnode.dev/why-a-finished-run-refuses-your-edits?utm_source=hashnode&utm_medium=feed)

Completing a test run locks it — 409, no edits of any kind. But the lock has deliberate holes: notes, evidence and defects stay open, because triaging a red run is exactly what those are for.

5 min read · [hawzu.hashnode.dev](https://hawzu.hashnode.dev/why-a-finished-run-refuses-your-edits?utm_source=hashnode&utm_medium=feed)

[Oct 2](https://hashnode.com/posts/why-a-finished-run-refuses-your-edits/6abf9d62ed2eb5efaf8dd2dd)

### [A Defect That Remembers the Step It Came From](https://hawzu.hashnode.dev/a-defect-that-remembers-the-step-it-came-from?utm_source=hashnode&utm_medium=feed)

Most defects are filed from a blank form and lose the run that produced them. Raising one from a step carries the reproduction path, the resolved data and the expected result — and records which step it came from.

5 min read · [hawzu.hashnode.dev](https://hawzu.hashnode.dev/a-defect-that-remembers-the-step-it-came-from?utm_source=hashnode&utm_medium=feed)

[Oct 2](https://hashnode.com/posts/a-defect-that-remembers-the-step-it-came-from/6abf9c8f726fc686d6eff9fa)

### [What a Test Run Actually Records](https://hawzu.hashnode.dev/what-a-test-run-actually-records?utm_source=hashnode&utm_medium=feed)

Store a test run as a list of pointers and the steps drift while the verdict stays put. Hawzu copies the test case into the run and pins its versions — which is what makes execution history mean anything.

6 min read · [hawzu.hashnode.dev](https://hawzu.hashnode.dev/what-a-test-run-actually-records?utm_source=hashnode&utm_medium=feed)

[Oct 2](https://hashnode.com/posts/what-a-test-run-actually-records/6abf9b8a94048a6b2b330db3)

### [QA Dashboards: Building One People Still Open in Month Three](https://hawzu.hashnode.dev/qa-dashboards-building-one-people-still-open-in-month-three?utm_source=hashnode&utm_medium=feed)

Most QA dashboards are built in week one and abandoned by month three. A guide to designing around decisions rather than available fields, the charts worth having, and the ones that quietly mislead.

7 min read · [hawzu.hashnode.dev](https://hawzu.hashnode.dev/qa-dashboards-building-one-people-still-open-in-month-three?utm_source=hashnode&utm_medium=feed)

[Oct 2](https://hashnode.com/posts/qa-dashboards-building-one-people-still-open-in-month-three/6abf9a5fabab942e0037531e)

### [QA Test Reporting: Reports People Actually Read](https://hawzu.hashnode.dev/qa-test-reporting-reports-people-actually-read?utm_source=hashnode&utm_medium=feed)

Most QA reports are written for nobody in particular and get skimmed once. A guide to choosing the report for the audience, the four numbers worth leading with, and why a report that recalculates isn't a record.

8 min read · [hawzu.hashnode.dev](https://hawzu.hashnode.dev/qa-test-reporting-reports-people-actually-read?utm_source=hashnode&utm_medium=feed)

[Oct 2](https://hashnode.com/posts/qa-test-reporting-reports-people-actually-read/6abf9901a4e1b65538cc0491)