『How to Test a Release – Oleksandr Bolzhelarskyi』のカバーアート

How to Test a Release – Oleksandr Bolzhelarskyi

How to Test a Release – Oleksandr Bolzhelarskyi

無料で聴く

ポッドキャストの詳細を見る

概要

Today, Oleksandr Bolzhelarskyi, Director of QA & Release Management at Salesfloor, shares why successful releases are impossible without responsible testing and quality management, and how teams can stop firefighting production bugs and start shipping with confidence.


👉 5 Golden Rules for a Successful Release


⛔ Testing features individually → ✅ Testing the release as a package Features that work perfectly in isolation can break when merged together. Two developers changing the same component won't know about each other's work until it's combined. Always retest the full package.


⛔ Bug bashes → ✅ Combining structured testing with fresh eyes.

Involving non-testers brings valuable perspective, but it's not systematic. Bug bashes catch random issues, not targeted risks. Use them as a complement, never as your only release testing.


⛔ Testing everything → ✅ Testing based on risk / product knowledge You'll never have time to cover everything. Know your product architecture, understand what the new changes could break, and focus regression testing where the real risks are.


⛔ Release pressure → ✅ Communicating untested risks clearly

Pressure to ship means the feature matters. Instead of pushing back emotionally, tell your manager: here's what we tested, here's what we didn't, and here's what could go wrong. Let them make an informed decision.


⛔ Allowing "one last quick fix" → ✅ Enforcing a strict code freeze Last-minute changes during regression testing cause the biggest surprises. Say no. If it's urgent, ship it as a hot fix after the current release is done.


Connect on LinkedIn: https://www.linkedin.com/in/oleksandr-bolzhelarskyi/

まだレビューはありません