--- title: "#release-management articles | Hashnode" description: "Explore 63 articles tagged #release-management on Hashnode. Tutorials, guides, and how-tos from the community." url: "https://hashnode.com/tag/release-management" --- Tag # #release-management 63 posts · 3 followers [pm25coder](https://hashnode.com/@pm25coder) · [Oct 22](https://hashnode.com/posts/how-many-places-does-your-project-s-version-number-live/6ad97cf34069ef078f105d14) ### [How many places does your project's version number live?](https://pm25coder.hashnode.dev/how-many-places-does-your-project-s-version-number-live?utm_source=hashnode&utm_medium=feed) Eight files in my repo declare the version, and one lockfile holds 334 fields named version. How to count the places, and make a miss fail loudly. 7 min read · [pm25coder.hashnode.dev](https://pm25coder.hashnode.dev/how-many-places-does-your-project-s-version-number-live?utm_source=hashnode&utm_medium=feed) [srinath](https://hashnode.com/@srinathy) · [Oct 2](https://hashnode.com/posts/why-a-finished-run-refuses-your-edits/6abf9d62ed2eb5efaf8dd2dd) ### [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) [srinath](https://hashnode.com/@srinathy) · [Oct 2](https://hashnode.com/posts/a-defect-that-remembers-the-step-it-came-from/6abf9c8f726fc686d6eff9fa) ### [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) [srinath](https://hashnode.com/@srinathy) · [Oct 2](https://hashnode.com/posts/what-a-test-run-actually-records/6abf9b8a94048a6b2b330db3) ### [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) [srinath](https://hashnode.com/@srinathy) · [Oct 2](https://hashnode.com/posts/qa-dashboards-building-one-people-still-open-in-month-three/6abf9a5fabab942e0037531e) ### [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) [srinath](https://hashnode.com/@srinathy) · [Oct 2](https://hashnode.com/posts/qa-test-reporting-reports-people-actually-read/6abf9901a4e1b65538cc0491) ### [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) [srinath](https://hashnode.com/@srinathy) · [Oct 2](https://hashnode.com/posts/managing-test-cases-in-excel-when-it-works-and-what-breaks/6abf97e8a7e285a7dec478df) ### [Managing Test Cases in Excel: When It Works, and What Breaks](https://hawzu.hashnode.dev/managing-test-cases-in-excel-when-it-works-and-what-breaks?utm_source=hashnode&utm_medium=feed) Spreadsheets are a reasonable place to start managing test cases. This is what they're genuinely good at, the four things that break as a team grows, and how to migrate without losing what you've built. 9 min read · [hawzu.hashnode.dev](https://hawzu.hashnode.dev/managing-test-cases-in-excel-when-it-works-and-what-breaks?utm_source=hashnode&utm_medium=feed) [srinath](https://hashnode.com/@srinathy) · [Oct 2](https://hashnode.com/posts/uat-test-management-running-acceptance-testing-in-a-qa-tool/6abf94c2758da2f6cf043ce7) ### [UAT Test Management: Running Acceptance Testing in a QA Tool](https://hawzu.hashnode.dev/uat-test-management-running-acceptance-testing-in-a-qa-tool?utm_source=hashnode&utm_medium=feed) A practical guide to managing user acceptance testing — scoping the cycle, giving business testers access without handing them a QA tool, tracking progress, and producing a sign-off artefact that still means something later. 10 min read · [hawzu.hashnode.dev](https://hawzu.hashnode.dev/uat-test-management-running-acceptance-testing-in-a-qa-tool?utm_source=hashnode&utm_medium=feed) [srinath](https://hashnode.com/@srinathy) · [Oct 2](https://hashnode.com/posts/defect-management-workflow-states-triage-and-the-handover-problem/6abf93e14874bd8ceb3b361b) ### [Defect Management Workflow: States, Triage and the Handover Problem](https://hawzu.hashnode.dev/defect-management-workflow-states-triage-and-the-handover-problem?utm_source=hashnode&utm_medium=feed) A guide to designing a defect workflow that survives contact with a real team — how many states you need, why priority and severity are different fields, and what breaks when bugs live in two systems. 9 min read · [hawzu.hashnode.dev](https://hawzu.hashnode.dev/defect-management-workflow-states-triage-and-the-handover-problem?utm_source=hashnode&utm_medium=feed) [srinath](https://hashnode.com/@srinathy) · [Oct 2](https://hashnode.com/posts/test-execution-tracking-what-80-executed-doesn-t-tell-you/6abf92fd81f375a951f622b9) ### [Test Execution Tracking: What "80% Executed" Doesn't Tell You](https://hawzu.hashnode.dev/test-execution-tracking-what-80-executed-doesn-t-tell-you?utm_source=hashnode&utm_medium=feed) A completion percentage says nothing about what's left, who holds it, or whether the date is still real. A guide to the statuses that carry information, why mid-cycle pass rate misleads, and what to track instead. 8 min read · [hawzu.hashnode.dev](https://hawzu.hashnode.dev/test-execution-tracking-what-80-executed-doesn-t-tell-you?utm_source=hashnode&utm_medium=feed)