System Test for a Call-Center Home Equity Loan Application
Rex Black staffed and led the independent test team for a bank's Release 1.0 home equity loan call-center application. Six weekly build cycles. Credit-scoring mainframe integration. A hard go-live date. Exit criteria that counted weeks without a crash, not days.
The Challenge
A new origination platform with a non-negotiable go-live date
The client needed a Release 1.0 home equity loan application deployed into a live call center inside a calendar quarter. The system integrated a Java / WebLogic front end, an Oracle database, a Netscape gateway, and a mainframe credit-scoring service accessed over MQ. Call Center agents would use it live, on the phone, with customers.
A failure in any of the integration points — scoring, application state, document generation at the downstream origination platform — would not just reject a loan; it would burn a real customer conversation. Negative business scenarios, capacity under concurrent agent load, and compatibility with the exact Fairbanks call-center desktop configuration all had to be covered in weeks, not months.
The bank had an in-house QA team and a beta program already running in Fairbanks, but needed an independent system-test organization with the discipline to run a fixed-date release to real exit criteria.
The Solution
A six-cycle system test program with hard criteria
Rex Black authored the system test plan and led the Minneapolis Test Group through six weekly build cycles. The plan defined exactly what was in scope (positive use cases, capacity, configuration, client desktop compatibility, scoring integration, origination status communication) and exactly what was not (negative use cases, localization, operations, documentation) so stakeholders never had to argue what "done" meant.
System test entry required the bug tracker in place, source and configuration under formal management, all environments stood up, unit test complete, and fewer than ten must-fix bugs open — all named, all auditable. Continuation criteria forced release notes on every build and twice-weekly bug reviews. Exit criteria required three consecutive weeks without a server-side crash or halt, all must-fix bugs resolved, and an open/close curve showing stability.
The test lab ran LoadRunner virtual-user clients for capacity and performance alongside cloned Call Center agent desktops for manual functional work. Three regions — the loan-app QA region, the scoring QA region, and the origination reference region — were used in every cycle to verify end-to-end loan flow against the legacy system as the reference oracle.
What we delivered
- +Master system test plan with IS / IS-NOT scope, definitions, and setting
- +Quality risks framed around positive use cases from the home equity business line
- +Schedule of milestones: unit test, smoke build, six build cycles, UAT, go-live
- +System test entry, continuation, and exit criteria tied to bug-backlog and release-notes discipline
- +Test configurations for LoadRunner virtual user clients and Call Center desktop clients
- +Test execution process: test cycles, human resources, escalation process with full contact list
- +Test case and bug tracking process, release management, risks and contingencies
By the Numbers
Shape of the engagement
Release 1.0, six build cycles, exit criteria that actually held.
Build Cycles
Six weekly release cycles from smoke build through golden build, each with regression + new-feature test coverage.
Stability Bar
System test exit required three consecutive weeks with zero server-side panic, crash, wedge, or halt.
Integrated Regions
WebLogic + Oracle + Netscape QA region, Scoring QA region, and the origination (reference) region.
Release
System test phase exited on schedule; UAT followed immediately and go-live landed on the planned date.
Outcome
System test exited on schedule. User Acceptance Test ran in the planned two-week window, and the go/no-go decision shipped on the date in the plan. The exit criteria held — the release was not rushed past the stability bar; the stability bar was met.
The test plan itself became the template reused on subsequent releases of the same product family and is available (scrubbed) as part of the QA Library.
From the QA Library
The test plan behind this engagement
The full, sanitized system test plan — the one actually used on this program — is available as a gated download in the QA Library.
System Test Plan
Home Equity Loan System Test Plan (Release 1.0)
Scope, quality risks, milestone schedule, transitions, environments, test execution process, escalation, and release management. The document that actually ran the program.
Fixed go-live date you cannot miss?
Independent system test with written entry, continuation, and exit criteria is how you hit a hard release without hiding risk.
Resources for this kind of program
Reading material that goes deeper on the methodology behind this engagement.
- Whitepaper
Evaluation Before Shipping: How to Test an AI Application Before It Hits Production
The release-gate playbook for AI features. Covers the five evaluation dimensions, how to build a lean golden set, where LLM-as-judge is trustworthy and where it lies, rollout mechanics with named exit criteria, and the regression suite that keeps a shipped AI feature from quietly rotting in production.
Read → - Whitepaper
Choosing the Right Model (and Knowing When to Switch)
A practical framework for matching LLM model tier to task. Covers the four axes (capability, latency, cost, reliability), cascade routing patterns that cut cost 60 to 80 percent without measurable quality loss, switching costs you did not plan for, and the worked economics at 10K, 100K, and 1M decisions per day.
Read → - Whitepaper
Beyond ISTQB: A Multi-Domain Certification Roadmap for Technical L&D
Most engineering L&D programs over-index on a single certification family, usually ISTQB on the QA side, AWS on the infrastructure side, and under-invest across the rest of the technical domains the org actually needs. This paper covers a multi-domain certification roadmap (QA, AI, cloud, data, security, project management, software engineering) with sequencing logic for each level of the engineering ladder, plus the maintenance discipline that keeps the roadmap relevant as the technology shifts underneath it.
Read → - Guide
The ISTQB Advanced Level path, mapped
The Advanced Level landscape keeps changing — CTAL-TA v4.0 shipped May 2025, CTAL-TM is on v3.0, CTAL-TAE is on v2.0. This guide maps all four core modules, prerequisites, exam formats, sunset dates, and which module a given role should take first. Links directly to the authoritative istqb.org syllabi.
Read → - Whitepaper
Bug Triage: A Cross-Functional Framework for Deciding Which Defects to Fix
Bug triage is the cross-functional decision process that converts raw defect reports into prioritized action. Done well, it optimizes limited engineering capacity against risk; done poorly, it becomes a backlog-management ritual that neither fixes the important defects nor drops the unimportant ones. This whitepaper covers the triage process, the participants, the six action outcomes, the four decision factors, and the governance disciplines that keep triage effective in continuous-delivery environments.
Read → - Whitepaper
Building Quality In: What Engineering Organizations Do from Day One
Testing at the end builds confidence, but the most efficient quality assurance is building the system the right way from day one. This whitepaper covers the upstream disciplines — requirements clarity, lifecycle selection, per-unit programmer practices, and continuous integration — that make system-level testing cheap and fast rather than the only thing holding a release together.
Read →
Want help running a program like this?
- Service · Quality engineering
Software Quality & Security
Independent test programs, security testing, and quality engineering for systems where defects cost real money.
Learn more → - Solution
Risk Reduction & Clear Decisions
Quality programs and decision frameworks that shift risk discussions from anecdote to evidence.
Learn more → - Solution
Reliable Software at Scale
Quality engineering programs for organizations whose software is now operationally critical.
Learn more → - Government
Government & Defense
ISTQB-based test programs and security testing for federal, defense, and public-sector software.
Learn more →