Notes on quality, and what we ship
Product updates, the thinking behind them, and field notes on quality engineering from the team building Tesbo.
All articles
How to Test Features That Give a Different Answer Every Time
AI features break the old rule of same input, same output. Here's how to write test cases around ranges instead of exact matches.
Ship Late or Ship Broken: How to Actually Make the Call
Every team hits the Thursday 6pm ship decision. Here's a framework for weighing delay cost against defect cost when you actually have ten minutes to decide.
Test Documentation for Regulated Industries
Regulated QA teams don't need more process. They need testing work that already leaves a record an outsider can follow. Here's what to keep.
Test Plan vs Test Strategy: The Difference That Matters
Test plans and test strategies get treated as synonyms, which is why plans get rewritten every sprint instead of pointing back to a strategy that never changes.
What Your Test Case Export Actually Loses When You Leave a Tool
Exports check that cases came out, not that evidence survives. Here is the twenty minute test to run before you find out the hard way.
Zephyr Scale Export: Keeping History and Traceability
Zephyr Scale's export handles case fields fine. Run history and traceability links need a plan. Here's the checklist that keeps them intact.
Linking a Test Case to a Bug Tracker Issue That Survives a Migration
A pasted bug tracker URL looks fine until the tracker migrates. Here is what linking a test case to a bug tracker issue needs to survive.
Xray Test Case Export: What Comes Out, What Gets Left Behind
Before you migrate off Xray, know what the export button leaves behind: run history, attachments, and field mappings need a real plan.
Test Management in Docker: The Compose File Is Only Day One
A docker compose up gets your test case manager running in minutes. Here is everything it quietly leaves you holding after that.
GitHub CI Meets Self-Hosted Test Management
A hosted GitHub runner can't reach a self-hosted test management instance behind your firewall. Three real ways to close that gap, with the trade-offs.
On-Premise Test Management: What the Requirement Actually Means Now
On-premise means different things to different buyers. Here's what the requirement actually asks for, and which deployment shape delivers it.
The Self Hosting Readiness Checklist for Test Case Management
A blunt, ten minute checklist for deciding whether your team should self host its test management tool, or admit it isn't ready yet.
Air-Gapped Test Management: Staying Auditable With No Route to the Internet
Air-gapped QA teams in defence, medtech and payments cannot lean on cloud tools. Here is what actually breaks, and what a tool has to do instead.
JUnit XML to a Case Record: Solving the Test Name to Case ID Mapping Problem
JUnit XML is the format every test runner speaks, but it never carries a case id. Here is how teams actually bridge that gap.
Kiwi TCMS vs TestRail: Where the Free Tier Actually Stops
Kiwi TCMS and TestRail both work. The real question is what Kiwi's free tier quietly cuts off, and what that costs once you hit it.
Open Core, Explained: How a Free Tier Gets Its Shape
Open core is a funding model, not a trick. Here is how to read any free tier in ten minutes, using Kiwi TCMS as the worked example.
Kiwi TCMS vs TestLink: Which Open Source Tool Fits Your Team
Kiwi TCMS and TestLink are both real, maintained, open source options. Here is which team each one actually fits, without a scorecard.
TDD vs BDD: Why Comparing Them Is Asking the Wrong Question
TDD and BDD get pitched as rivals, but they solve different problems at different levels. Here is how they actually fit together.
Vendor lock-in in test management: it's not the licence
Vendor lock-in in test management is a data-shape problem, not a licence problem. Here's what fails to export, and how to check before you commit.
Run a Migration Dry Run Before You Pick a Cutover Date
A QA lead's step by step dry run procedure that turns a migration guess into a defensible number before any date gets promised.
Test Suite Storage Sizing: How Big Does a Suite Get on Disk?
Test case text barely takes any space. Attachments do, and they grow with every run. Here is the arithmetic to size storage before the volume fills up.
Test History Backup: Why a Backup You Have Never Restored Is Not a Backup
Your test history backup is audit evidence, not just data. Here is the backup plan and the quarterly restore drill that proves it works.
TestLink vs TestRail: The Real Cost Question
TestLink or TestRail isn't a feature fight. It's a licence fee versus operational hours question, and the right answer depends on team size.
TestLink and Kiwi TCMS Alternatives: When to Move On
Already decided to leave TestLink or Kiwi TCMS? Here is the real moment each stops fitting, what a migration actually costs, and where to land.
How to Build a Cross Browser Test Matrix Without Buying a Grid
A practical way to pick which browser and OS combinations actually deserve a permanent slot in your test matrix, using your own analytics.
Estimating QA Effort for AI Features You Can't Predict
AI features break test-count estimates because output changes every run. Here is a method built on behaviours instead, with a worked example.
Shift-Left Testing: What Actually Moves Earlier, and What Never Can
Shift-left testing gets sold as a mindset. Here is the narrow, actionable version: which artefacts genuinely move earlier, and which testing work cannot.
Open Source Test Case Management: The Free Tier Trap
Open source test case management sounds free. Here is what a real, dated, checkable free tier actually withholds and how to check any tool yourself.
How to Export Test Cases From TestRail: The Export, Map, and Verify Playbook
A step by step guide to export test cases from TestRail, map fields correctly, and verify the import actually worked.
Test Plan vs Test Strategy: How to Tell Them Apart and Use Both Well
Test plan and test strategy get used interchangeably, but mixing them up costs QA leads real planning time every release. Here is the difference.
Manual Testing vs Automation Testing: Why It's the Wrong Question
Manual vs automated testing isn't a competition to win. See how QA leads decide, test by test, which approach actually belongs where.
Verification vs Validation: The Distinction That Only Matters in Regulated Work
Verification and validation sound interchangeable until an auditor asks for separate evidence. Here is where the line actually matters.
Edge Cases: Finding the Ones Worth Writing Down
Edge cases are infinite, so the real skill is deciding which ones earn a permanent test case. Cost of failure times plausibility is how you draw the line.
Happy Path Testing: The Case a Non-Tester Will Actually Read
Happy path testing rarely finds bugs, but it's the one test case a product manager, support engineer, or auditor will actually read. Write it carefully.
Writing Acceptance Criteria That Turn Into Test Cases
Vague acceptance criteria don't just read badly, they produce test cases nobody agrees on. Here's the same story written badly and well, side by side.
Alpha vs Beta Testing: What to Do With the Feedback After
Every guide to alpha vs beta testing stops at the comparison. The real work starts after: triaging feedback into a defect, a new case, or a deliberate no.
How to Create a Test Plan: A Step-by-Step Guide With Examples
A step-by-step guide to writing a test plan that stays useful after day one, with a worked example and a template you can reuse.
Acceptance Testing and UAT: Who Actually Signs Off
Acceptance testing and UAT are the only testing defined by who signs off, not what they cover. Here's how to write cases each signer will actually approve.
The Software Testing Life Cycle: Why It Runs Beside Development, Not After It
STLC is not a checklist that starts once coding wraps. See how each phase runs alongside the SDLC, plus best practices that catch gaps early.
The Exploratory Test Charter Template You Can Copy Today
A ready-to-use exploratory test charter template with a worked example, so your next session has a target instead of aimless clicking.
The Test Execution Report Template You Can Use By Friday
A ready to use test execution report template: summary, scope, failures, blocked cases, and sign off, so you stop rebuilding it every release.
The Flaky Test Triage Runbook: What To Do In The First 30 Minutes
The 30 minutes after a build goes red for no reason. A step by step runbook: reproduce, isolate, classify, quarantine or fix, close the loop.
Open Source or Commercial Test Management: A Four Question Method
A four question method for choosing open source or commercial test management, one that sometimes tells you to buy the commercial tool.
Software Testing Tools by Role: What QA, Developers, and DevOps Each Actually Need
Software testing tools grouped by who actually uses them: QA, developers, and DevOps each need a different kind of tool, not one ranked list.
GPL vs Apache Licence: What You Owe When You Self Host
GPL and Apache 2.0 are both genuinely open. The difference matters only in three specific situations, and this post covers exactly those.
Migrating Off Kiwi TCMS: The Free Tier Route Through the API
Kiwi TCMS has a real API, which makes leaving it easier than most. The complications are tier shaped, not technical, and this post walks the free route out.
The Test Case Review Checklist That Actually Gets Used
Most test case reviews are a rubber stamp. Here's a checklist short enough to run on every case, under a minute each, that actually catches problems.
Azure Test Plans Alternatives: When the Built-In Tool Stops Being Enough
Azure Test Plans is narrow by design, not badly built. Here is exactly where teams outgrow it, and what it actually costs to leave.
Who Runs the AI When You Self Host Your Test Cases
Self hosting keeps data on your server, but an AI feature can still send test case content to a third party. Here is how bring your own key fixes that.
Performance Testing: Write Down What "Fast Enough" Means Before You Run Anything
Performance testing usually fails before the load tool even starts, because nobody wrote down what fast enough meant. Here is how to fix that.
Regression Testing: Types, Process, and How to Pick a Smaller Suite
A practical guide to regression testing types, techniques, and process, focused on choosing the right subset of tests instead of re-running everything.
Top 15 Test Management Tools for Modern QA Teams in 2026
Explore 15 test management tools to streamline QA workflows, improve test coverage, and find the right fit for your team.
Human in the Loop Test Case Review: Why Reviewing Is a Skill
"Human in the loop" gets said as reassurance, not design. Here are the three ways review actually fails, and what a queue must show to stop them.
The Manual to Automation Testing Transition, Explained
Moving from manual to automation testing isn't about learning to code. It's about writing test cases precise enough for a script to run.
TestLink Migration: What the XML Export Actually Carries
Before you promise anyone a cutover date, know what TestLink's XML export carries, what it drops, and the ordered plan that keeps the migration honest.
Data Residency for Test Cases: A Checklist for QA Leaders
A customer contract asks where your test data lives. Here's what residency really means for test cases, run history, and the vendors you rely on.
Monkey Testing: From Random Crash to Reusable Case
Monkey testing finds crashes cheaply, but only pays off if the crash becomes a reproducible test case. Here's how that handoff works.
Where Your Load Testing Target Number Should Actually Come From
Most load tests run against a number someone guessed in a meeting. Here's how to derive a defensible target from real traffic instead.
What a Customer's Security Questionnaire Is Actually Testing
Enterprise security reviews aren't really about your controls. They're about whether you can produce evidence in a day, not three weeks.
After TestOps: Where the Record Goes When Agents Run Tests
As AI agents propose and run tests, human judgment shrinks to one act: approval. Here's why that log becomes the record that matters.
Every release, in plain language
What shipped, what changed, and why we chose it. No version notes written for machines.
See tested, untested, and risky areas per suite, with run history behind every number.
Zyra turns a failure into a structured report with logs and steps, queued for your approval.
Bring an existing repository across with suites, priorities, and owners intact.
Every AI draft carries who approved it, when, and what changed before it entered the suite.
One page, one idea
-1-900x600.png%3Fprefix%3Dprod&w=3840&q=75)
-1-900x600.png%3Fprefix%3Dprod&w=3840&q=75)
Start here if you are new to Tesbo
Four short guides that take you from an empty project to a reviewed suite and a first run.
Test cases for the features every product has
Coverage baselines for login, checkout, APIs and the rest — including the negative, security and accessibility cases most published sets leave out. Free, and every set says where it came from.
Browse the library
One email a month. Releases and one good idea.
What we shipped, what we learned, and the occasional infographic worth pinning. Unsubscribe in one click.