How TBI Bank Replaced 20+ Scattered Excel Sheets with 1085 Structured Test Cases and an Automated QA Pipeline using Tuskr
The Challenge
TBI Bank’s test documentation was spread across more than 20 separate Excel sheets. The QA team had no central view of test coverage, failures, completed testing, or outstanding work. Test cases, test runs, and results were disconnected.
- One Excel sheet per feature, spread across the organization’s shared storage
- No way to see total test coverage across the whole product at a glance
- No reliable view of what had been tested, what had failed, or what remained open
Key Results
TBI Bank built a fully connected QA pipeline on top of Tuskr’s integrations and AI capabilities, replacing a fragmented Excel based system with a single source of truth.
Structured test cases in one place
replacing 20+ scattered Excel sheets
Pass rate tracked in real time
across active test runs in Tuskr
About the Client
TBI Bank
Founded 2002 · Sofia, Bulgaria
A mobile-first challenger bank and regional leader in alternative payment solutions across Southeast Europe. TBI Bank serves 2.4 million customers through partnerships with over 38,000 merchant stores across six markets A banking product at that scale means a fast-moving QA process is not optional. But speed without visibility creates risk. That is exactly what TBI Bank's QA team was up against before Tuskr.
Financial Services & Challenger Banking
1,000–2,000 employees Sofia, Bulgaria
The challenge: 20+ Excel sheets, one per feature, with no central view of coverage
Before Tuskr, TBI Bank’s test documentation was spread across the organization’s shared storage in the worst possible format: one Excel sheet per feature.
The problem was not just volume. It was visibility. With test cases scattered across dozens of disconnected files, no one could see total coverage at a glance. There was no way to track what had been tested, what had failed, or what was still outstanding across the whole product.
For a bank shipping digital financial products to millions of customers, that kind of blind spot carries real risk.
“Lack of test cases, and the few that existed were written in some Excel sheets spread across the organization storage.”
Yordan Nedelchev, Senior Automation QA Engineer at TBI Bank
The Key Challenges
One sheet per feature
Every feature had its own Excel file, with no shared structure tying them together.
20+ disconnected files
Test documentation was fragmented across more than 20 spreadsheets with no single consolidated view.
No coverage visibility
No one could see total test coverage across the whole product at a glance.
No failure or progress tracking
There was no reliable way to track what had failed or what testing was still outstanding.
The solution: a fully automated QA pipeline on top of Tuskr
TBI Bank did not just migrate test cases into Tuskr. They built a pipeline on top of it. When Azure finishes an automation run, the test report is forwarded to Tuskr via the Playwright integration and uploaded directly as a Test Run. No manual upload, no copy-paste. The results appear in Tuskr automatically.
When a test case is marked as failed, the Jira integration fires. A bug is opened in Jira automatically, based on the team’s configuration in Make.com. The whole loop—from Azure run to Jira ticket—runs without manual handoffs.
On top of that automation layer, Yordan built a custom AI assistant to produce test cases and generate import-ready files for Tuskr, handling the authoring volume that would otherwise require hours of manual work per feature.
Tuskr's support team has also shaped how the platform works for TBI Bank specifically. They improved reporting capabilities based on Yordan's feedback and helped resolve integration issues that emerged during setup. The product improved because the team asked for it and the support team acted on it
Tuskr features used
- Test Cases
- Test Runs
- AI Test Case Creation
- Playwright & Jira Integrations
When the Azure finishes its run, the test report is forwarded via the Playwright integration to Tuskr and uploaded as a Test Run. Also when we mark a test case as failed, the Jira integration is executed and a bug is opened in Jira based on our configuration at Make.com.
What TBI Bank needed
Affordable pricing
Inside a large bank, QA teams often run small. The cost of a test management platform had to match the team's actual size, not an enterprise headcount it didn't have.
Native integrations
TBI Bank's automation stack was already defined. Any tool that couldn't connect to all three was a step backwards, not forwards.
AI for test case creation
The volume of test cases needed to cover a banking product across six markets made manual authoring a genuine bottleneck. A tool with AI-assisted creation was a requirement, not a bonus.
Responsive support
Tuskr's support "was responding quickly, accurate and took into consideration our needs which lead to feature improvements." For a bank with specific integration requirements, that responsiveness was a deciding factor.
The results: real-time coverage visibility, automated bug creation, and QA that scales
The transformation from Excel to Tuskr changed what TBI Bank’s QA team can actually see and act on. Test coverage is no longer a guess.
The team’s Syncro project shows 546 test cases across 15 test suites, with 210 active test runs and an 89% pass rate tracked live. When something fails, a Jira bug is already open before anyone has to log it manually. When Azure finishes a run, the results are already in Tuskr.
Much well structured test case database, and visible and measurable quality coverage.
I have built an AI assistant to produce test cases and generate import-ready files, Yordan said. I could not estimate the time saved, but it's far better than Excel.
The shift from scattered sheets to a structured, integrated system means TBI Bank’s QA team now has the same thing the rest of the bank runs on: a single source of truth, with real-time data and automated handoffs. “The price and the features provided for it are unmatched on the market,” Yordan said.
From 20+ disconnected Excel files to 1,085 test cases tracked in one place, with an 89% pass rate visible in real time.
After Tuskr
- 1,085 structured test cases replace 20+ scattered Excel sheets.
- 89% pass rate tracked in real time across active test runs.
- Azure automation results flow into Tuskr automatically via Playwright.
- Failed test cases open Jira bugs automatically through Make.com.
- AI-assisted test case authoring replaces hours of manual Excel work.
- Quality coverage is visible, measurable, and centralized in one place.
See how Tuskr works for banking and fintech QA teams
If your QA team is still tracking test cases in feature-by-feature spreadsheets, Tuskr gives you a structured, integration-ready alternative that connects your automation stack end to end.
