QF-Test with extensive experience testing banking software

In banking, there’s zero tolerance for software errors: account transactions, credit decisions, securities orders, pension management – a single bug can put customers, compliance, and reputation at risk.

At the same time, IT teams at banks and financial service providers are under considerable pressure: legacy systems built on Java Swing run alongside modern web portals, regulatory requirements such as MaRisk, BAIT, and DORA force continuous software changes, and every new release must be fully tested – often with limited resources and tight deadlines.

This is where QF-Test comes in: with automated UI tests, regression tests, and AI-assisted testing, QF-Test ensures that your banking software works reliably with every release and after every regulatory change – across Java frontends, web portals, and legacy systems alike.

Banking and financial services reference customers

HPVB+S Bankensysteme

Everything you need for effective test automation of banking software

Reliable object identification
QF-Test stands for robust component recognition & infrequent maintenance.
Daily regression tests
Monitoring of the test results for documented good software quality & a good feeling..
Flexible integrations
Common tools like Jira, Jenkins, databases, Git can be linked with QF-Test.
Customizable report
Individualizable tests

Typical challenges when testing banking software

Banking software is among the most complex and security-critical application classes of all. Errors in credit calculations, booking workflows, or customer data portals can cause financial damage – and put customer trust and regulatory standing at risk.

Heterogeneous landscapes of legacy and web systems
Many banks run grown IT landscapes: Java Swing clients for the core banking system run alongside modern web portals for online banking. QF-Test supports all these technologies in a single testing tool – with no tool sprawl and a shared test base for every interface.
Mission-critical processes with zero tolerance for errors
Account management, payment processing, lending, securities transactions, pension calculations – errors in these processes are not an option. QF-Test can monitor mission-critical banking workflows automatically every day and raise the alarm before any error reaches production.
Consistent tests across systems and clients
Banking software often spans multiple clients, regional versions, and system interfaces simultaneously. QF-Test enables end-to-end tests across system boundaries – automated and reproducible, from the core system through the portal to the accounting interface.

Hamburger Pensionsverwaltung eG logo

Hamburger Pensionsverwaltung eG (HPV) manages pension entitlements and funds for its member companies, overseeing assets of more than seven billion euros and close to half a million pension commitments. Reliable software here is quite literally not optional.

HPV has been using QF-Test since 2010 – testing both its web-based portal applications and its Java-based inventory management system in a single, unified testing tool. Particularly valuable: consistent end-to-end tests across both systems – catching errors at the interface between portal and inventory system before they reach production.

Previously, HPV had used Selenium, but the maintenance burden after just a few major versions became so high that the team abandoned the tool. With QF-Test, HPV found a stable, low-maintenance alternative – and is now considering extending QF-Test to cover testing of the organization’s own website as well.

“Since 2010 we’ve been able to test our portal applications comfortably. We also test our Java-based inventory management system with QF-Test. Since then we can also run consistent tests between the inventory management system and the portal applications.”
Attila Enez,
Tester, Hamburger Pensionsverwaltung eG

B+S Banksysteme AG logo

B+S Banksysteme Aktiengesellschaft develops software solutions for banks and financial service providers.

QF-Test has been an integral part of B+S’s development and quality processes since 2006 – starting with automated regression and integration tests for the Java Swing interface of the banking software, then steadily expanded: following an acquisition, native web applications were added to the scope and are now tested with QF-Test as well.

QF-Test is deployed across the entire group at B+S, covering development and integration tests, nightly build regression tests, and customer-specific acceptance tests prior to delivery. A particularly relevant topic was the migration to WebSwing: QFS was already working on WebSwing support when B+S had the requirement – the collaboration enabled a smooth integration of tests across the technology change.

“The straightforward development of test procedures and test cases convinced us very quickly and also ensured a very high level of acceptance among employees – both those who develop the tests and those who run them. We especially want to highlight the stable component recognition despite the continuous development of UI elements and Java versions.”
Team B+S Banksysteme AG,
Munich, Germany

Banking icon
Want to automate testing for your banking software?

Put QF-Test to work for the quality assurance of your financial applications!

Try QF-Test for free, or contact us to schedule a demo webinar with one of our experienced experts.

Test automation as a response to regulatory requirements in banking

Banking is one of the most heavily regulated industries in the US and internationally. Regulators and supervisory frameworks place concrete requirements on the quality assurance of IT systems – demanding not just working software, but documented proof of its quality.

Verifiable software quality

Internal audits, regulatory examinations, and external reviews require structured, reproducible quality evidence. After every test run, QF-Test automatically generates detailed test reports (HTML or XML) that document which processes were tested, when, and with what results – structured and traceable, as part of the documentation for internal audits and reviews.

MaRisk and BAIT: IT requirements from banking supervisors

The Minimum Requirements for Risk Management (MaRisk) and the Supervisory Requirements for IT in Financial Institutions (BAIT) oblige credit institutions to maintain adequate IT risk management – including verifiable quality assurance for business-critical applications. Every software change in the core banking environment must be fully tested and documented. Automated regression tests with QF-Test deliver structured test documentation after every release that can be used as part of quality evidence.

DORA: digital operational resilience as a regulatory obligation

The EU’s Digital Operational Resilience Act (DORA) has set binding requirements for the digital resilience of financial institutions since 2025 – including structured testing of ICT risks. Automated UI regression tests can be one building block in supporting DORA’s quality assurance requirements – particularly for applications with regulatory relevance. DORA also covers other areas such as incident management and infrastructure resilience that go beyond UI testing.

Internal control systems (ICS) and SOX

For publicly listed banks and financial service providers, a functioning internal control system (ICS) is mandatory – internationally often required under the Sarbanes-Oxley Act (SOX). Automated tests with QF-Test document transparently that critical financial processes such as payment approvals, booking workflows, or credit authorizations were tested and that results are reproducibly available – and that errors are caught early, before they affect business operations or audit outcomes.

GDPR-compliant use

Banking software processes highly sensitive personal data: account information, credit data, income details, pension entitlements. QF-Test runs entirely within your own IT infrastructure – test data never leaves your organization. There are no cloud dependencies and no data transfers to third parties. This significantly simplifies privacy-compliant use and supports compliance with data subject rights obligations in the testing process.

Case studies from long-standing QF-Test users in banking

“Since 2010 we’ve been able to test our portal applications comfortably. We also test our Java-based inventory management system with QF-Test. Since then we can also run consistent tests between the inventory management system and the portal applications.”
Attila Enez,
Tester, Hamburger Pensionsverwaltung eG
“The straightforward development of test procedures and test cases convinced us very quickly and also ensured a very high level of acceptance among employees – both those who develop the tests and those who run them.”
Team B+S Banksysteme AG,
Munich, Germany

FAQ

Frequently asked questions: Test automation in banking

Why is QF-Test especially well suited for banking software?

Years of hands-on experience in financial services, tests that stay stable despite frequent releases, and built-in compliance evidence – QF-Test understands the demands of banks and financial service providers.

Extensive industry experience: Financial institutions such as Hamburger Pensionsverwaltung eG and B+S Banksysteme AG have relied on QF-Test for many years – with proven solutions for typical banking scenarios.

Stability despite frequent changes: Robust component recognition keeps tests stable even after UI changes, framework migrations (e.g. Java Swing → WebSwing), or release upgrades.

Built-in compliance evidence: Automatically generated test reports support documentation for regulatory examinations, internal audits, and frameworks such as MaRisk, BAIT, and DORA.

Data privacy through on-premise deployment: QF-Test runs locally within your own infrastructure – sensitive financial and customer data never leaves your organization.

Long-term ROI: B+S Banksysteme has been using QF-Test successfully since 2006 – test suites built once run stably for years.

Which banking applications can QF-Test test?

QF-Test supports Java-based fat clients as well as modern web portals and WebSwing applications – all within a single testing tool.

QF-Test tests banking software through its graphical user interface – regardless of whether it is implemented as a Java application (Swing, JavaFX, SWT) or as a web application. This covers core banking systems, online banking portals, inventory management systems, credit decision systems, and other financial applications. The flexible component recognition can be adapted to virtually any banking application.

How does QF-Test support MaRisk, BAIT, and DORA requirements?

Automated tests and comprehensive test reports deliver the evidence that regulators and internal auditors require.

After every test run, QF-Test generates detailed reports (HTML or XML) documenting which processes were tested, when, and with what results. These reports can be used as part of quality documentation for internal reviews and audits – for example within the scope of MaRisk, BAIT, or DORA. Whether they are sufficient in the specific audit context depends on the respective QM system and internal processes. The same applies to cross-industry requirements such as SOX or ISO 27001.

How stable are tests during frequent releases or technology migrations?

QF-Test is known for its robust component recognition – a key advantage in an industry that runs legacy systems and modern web frontends side by side.

QF-Test’s intelligent object recognition identifies UI elements based on multiple characteristics – not just IDs or positions. This makes tests significantly more robust against UI changes, framework updates, and release cycles. B+S Banksysteme explicitly highlights the stable component recognition despite continuous development of UI elements and Java versions as a central advantage. During migrations, existing test suites can often largely be reused.

Can QF-Test run end-to-end processes across multiple systems?

Yes – QF-Test tests complete financial processes across system boundaries, automatically and reproducibly.

Hamburger Pensionsverwaltung eG uses QF-Test for exactly this: consistent end-to-end tests between the Java-based inventory management system and the web portal applications. Errors at system interfaces are caught early – before they affect production or audit reports.

How quickly does QF-Test pay for itself in a banking environment?

Many customers report noticeable relief within just a few months – especially when recurring regression tests follow releases and regulatory changes.

Test suites built once run stably for years, replacing costly manual regression testing after every release or regulatory update. The larger the share of recurring test tasks – booking workflows, payment approvals, product configurations – the faster the investment pays off. B+S Banksysteme has been using QF-Test group-wide since 2006; Hamburger Pensionsverwaltung since 2010.

Can QF-Test be used by functional testers without programming skills?

Yes – keyword-driven testing lets you build and maintain tests without writing a single line of code.

With the keyword-driven testing approach, functional testers can define test cases in a clear, table-based format – no coding required. Developers set up the technical keywords once; the QA team uses them flexibly. In banking, this is especially valuable: subject matter experts from credit, securities, or pension administration are often the best testers for their own processes.

How much effort does it take to introduce QF-Test in an existing bank?

Rollout can happen incrementally – no big-bang migration required, and no disruption to ongoing processes.

QF-Test can be introduced step by step: starting with a pilot project for a single application or core process, then expanded incrementally. Quality First Software supports the onboarding with training, consulting, and workshops – so the start goes as smoothly as possible, even in complex, grown IT landscapes.

How does QF-Test integrate with existing CI/CD pipelines like Jenkins or GitLab?

QF-Test is designed for modern DevOps environments and integrates seamlessly with common CI systems.

QF-Test offers native support for common CI/CD tools such as Jenkins, GitLab CI, and Bamboo. Tests can be executed fully automatically as part of the build process, with results fed directly into your existing reporting and ticketing systems such as Jira. Every software release is automatically checked for quality – with results immediately available for both the team and auditors.

Can QF-Test check PDF documents such as account statements or loan decisions?

Yes – QF-Test can automatically verify whether generated PDF documents are correct and complete.

Banking software continuously generates PDF documents: account statements, loan decisions, annual reports, product information sheets. With QF-Test’s PDF testing feature, these documents can be automatically checked for content, structure, and computational accuracy – for example, whether balances are correct, required fields are present, or legally mandated disclosures are properly rendered. This eliminates time-consuming manual review after every release.

Is using QF-Test compliant with data privacy regulations?

Yes – QF-Test runs locally within your own infrastructure and does not transfer any test data to external services.

Because QF-Test is deployed entirely on-premise, highly sensitive financial data – account information, credit data, pension entitlements, customer records – never leaves your organization’s infrastructure at any point. There are no cloud dependencies and no data transfers to third parties. For banks and financial service providers, this is an important prerequisite and significantly simplifies compliance with data subject rights obligations in the testing process.

We use "Matomo" cookies to anonymously evaluate your visit to our website. For this we need your consent, which is valid for twelve months.

Cookie Configuration

Functional cookies

We use functional cookies to ensure the basic functionality of the website.

Performance and statistics cookies

We use Matomo for analyzing and optimizing our website. Cookies permit an anonymous collection of information that help us offering you a clear and user-friendly visit of our web pages.

Cookie details
Description Vendor Lifetime Type Purpose
_pk_id Matomo 13 Months HTTP Contains a unique, pseudonymized visitor ID internal to Matomo for recognizing returning visitors.
_pk_ref Matomo 6 Months HTTP Used to track from which website the anonymized user proceeded to our website.
_pk_ses Matomo 1 Day HTTP The Matomo session cookie is used to track the visitor's page requests during the session.
_pk_testcookie Matomo Session HTTP Used to check whether the visitor's browser supports cookies.
_pk_cvar Matomo 30 Minutes HTTP Temporarily store data about the visit.
_pk_hsr Matomo 30 Minutes HTTP Temporarily store data about the visit.