Business-driven test automation

The transformation of traditional test structures in companies is increasingly being shaped by methodically integrated specialist departments. One example shows how employees without an IT background are gradually introduced to test automation - with familiar tools, adapted wording and systematic coaching approaches. The aim is to integrate specialist knowledge directly into quality assurance and to reduce time-consuming manual testing in the long term. The focus is on risk-based and business-driven testing, accompanied by a culture of continuous improvement. This creates processes that not only increase efficiency, but also strengthen the understanding of software quality throughout the company.

Podcast Episode: Business-driven test automation

In this episode, I talk to Jörg "Jogi" Sievers from Signal Iduna about business-driven test automation. Jogi shows us how specialist departments can be effectively integrated into test automation despite their day-to-day duties. With a lot of pragmatism, a good dose of humor and clever approaches - for example, using familiar metaphors such as "rail replacement traffic" - he manages to make testing more accessible.

"We ask the people who are going to use the tool. That's the only way to create real acceptance." - Jörg Sievers

Jogi has been a specialist in test automation and software quality assurance for over 25 years. Before that, he worked in the food industry for a decade, where his eye for quality was sharpened from the very beginning. In his private life, he specialized in remote data transmission (bulletin board systems (BBS), also known as mailboxes) in the pre-Internet age, until he finally landed in IT. Installations, migrations, support and training for medical practice software, as well as the sale and installation of PCs, NeXT, Sun and Apple computers gave him a broad base of IT knowledge. This was followed by the surface test automation of StarOffice and OpenOffice.org as desktop applications and Sun WebOffice in the web world. He then worked for ten years for a software manufacturer and service provider in the energy industry before joining the SIGNAL IDUNA Group four years ago.

Highlights of the Episode

• Specialist departments have been successfully integrated into test automation
• Test methodology is based on risk-based scenarios instead of historical data sets
• Test language and principles were made easy to understand through adapted metaphors
• Coaching approach with ensemble testing ensures sustainable test competence
• Synthetic test data generation and contract testing are key future goals

Test automation with a business focus

Introduction to business-driven test automation

Business-driven test automation is becoming increasingly important in the insurance context. At Signal Iduna, this approach was implemented specifically to meet the special requirements of the industry. Test automation in the insurance environment requires not only technical know-how, but also a deep technical understanding of business processes and regulatory requirements.

Previous automation attempts at Signal Iduna had to contend with considerable challenges. Testing was mainly carried out by teams of developers who often lacked the necessary insurance-specific expertise. This meant that important technical aspects and industry-specific risks were not adequately covered. Purely technical testing reached its limits when the focus was on complex insurance products and regulatory compliance.

The introduction of business-driven test automation eliminated this gap through close collaboration between technicians and business experts. This ensured that automated testers not only checked technical functionalities, but also validated the correct behavior from an insurance business perspective. This was a decisive step towards higher quality and audit-compliant test automation at Signal Iduna.

Framework conditions and requirements in the insurance industry

Compliance with the VAIT (Insurance Supervisory Requirements for IT) is a central challenge for test automation in the insurance industry. Testing under VAIT requires both technical and functional approvals to ensure that systems comply with regulatory requirements.

Technical approvals

Technical approvals** are often granted by insurance brokers or experts whose knowledge is essential for a sound assessment.

Technical approvals

Technical insurance knowledge is necessary to correctly map the complexity of products and processes and to accurately assess risks.

To ensure audit-compliant documentation, a tool was deliberately chosen that enables Excel-like operation. This form of documentation not only makes it easier to provide evidence to auditors, but also supports the traceability and transparency of all test activities. This approach ensures both technical and professional quality assurance.

Selection and introduction of the test tools at Signal Iduna

The selection process for the test tools was carried out by two technically experienced employees who used usability testing as a decisive criterion.

Half-day training sessions were held to clearly define the test objectives and establish a risk-based approach.

Test automation was introduced in line with the adapted Kiterra four-pillar strategy. This test automation has now developed from an optional extra to an obligation and significantly increases efficiency in quality assurance.

Organizational structure and team composition for test automation

The organizational structure at Signal Iduna has evolved through an agile transformation since 2019. This includes the integration of business analysts in cross-functional teams to ensure a more holistic approach. In addition, a coaching model has been implemented that provides for weekly team coaching sessions and ensemble testing in the Center of Excellence since September.

The teams are composed in such a way that they include both technicians with automation experience and technical experts. This mix ensures a broad spectrum of expertise and technical competence for the effective implementation of business-driven test automation.

Principles and methods of test automation at Signal Iduna

In test automation, Signal Iduna relies on proven principles such as the Triple A principle, which consists of the steps Arrange, Act and Assert. The initial situation is prepared first (Arrange), then the action is executed (Act) and finally the result is appraised (Assert). In addition, the Rail Replacement Service is used, which follows a structured procedure with the Setup, Execute and Verify phases.

Business-driven test automation is based on a behavior-based approach that is particularly suitable for complex insurance projects. This focus on the expected behavior of the software makes testing more precise and meaningful.

A central component is risk-based training, which teaches practical examples such as equivalence partitioning and boundary value analysis. These trainings support teams in identifying critical scenarios and testing them efficiently, which sustainably increases the quality of automation.

In addition to implementing these principles and methods, a transition to open source test automation could be considered. This type of test automation can be challenging, but moving to open source solutions increases efficiency and significantly reduces manual intervention. For a deeper insight into the concepts, methods and techniques of test automation, I recommend the book by Richard Seidl, which provides comprehensive basic knowledge to make testing more efficient.

Successful projects and practical experience in business-driven test automation at Signal Iduna

The automation of the customer portal for digital correspondence and product purchases is one of the outstanding successes at Signal Iduna. This project has been running stably for over 3.5 years without any abnormal ends and shows how sustainable test automation can be implemented.

The optimization of the login behavior in the portal, which improved user-friendliness and security, was essential for the success. The automation enabled a significant reduction in effort, as communication between developers and specialist testers became noticeably more efficient.

The test automation of different system types played a crucial role in this process. The close cooperation between the teams ensured that technical requirements could be precisely translated into automated tests. This not only increased the quality of the software, but also ensured the maintainability of the tests.

Practice has shown that continuous automation and coordinated processes can save resources in the long term - a clear benefit for the entire company.

Technical aspects, tool comparison and data management in business-driven test automation at Signal Iduna

The business-driven test automation at Signal Iduna includes the comparison of two different tools for different application purposes:

• Cypress: Suitable for one-pager apps that have specific test automation requirements.
• Sahi Pro: Better suited for system changes and interaction with other systems.

Care is taken to ensure that testers use simple programming languages, while developers use JavaScript. This combination improves collaboration between teams and enables efficient implementation of test cases.

Future prospects for business-driven test automation in an agile context at Signal Iduna

The further development of business-driven test automation at Signal Iduna is based on consistent agile adaptation. A central focus is on synthetic test data generation in order to make quality assurance even more efficient and flexible. By generating artificial but realistic data, tests can be carried out independently of real production data, which improves both data protection aspects and the availability of test data.

The motivation to share successful experiences from previous projects serves as an important incentive for continuous improvement. This openness promotes increased acceptance of automation solutions in the teams and supports the establishment of a sustainable test strategy. The combination of agile working methods and innovative techniques such as synthetic data generation strengthens the role of business-driven test automation as an integral part of modern software development in the insurance environment.

Frequently asked Questions

What is meant by business-driven test automation in the insurance context?

Business-driven test automation at Signal Iduna means that test automation is closely aligned with business requirements and processes. It combines business expertise and technical automation to ensure high-quality testing that is specifically tailored to the insurance industry.

What are the framework conditions and requirements for test automation in the insurance industry under VAIT?

Under VAIT (Insurance Supervisory Requirements for IT), both technical and functional approvals are mandatory. Insurance expertise plays a central role, especially in the selection of audit-compliant tools with Excel-like documentation to ensure audit documentation and fulfill compliance requirements.

How were the test tools selected and introduced at Signal Iduna?

The tool selection was made by two technically experienced employees based on usability testing, with a focus on user-friendliness. Half-day training sessions clarified test objectives and the risk-based approach. The introduction was based on the Kiterra four-pillar strategy to ensure a structured implementation of test automation.

What is the organizational structure for business-driven test automation at Signal Iduna?

Since 2019, an agile transformation has been taking place with cross-functional teams in which business analysts are integrated. A Center of Excellence provides support with a coaching model including weekly team coaching sessions and ensemble testing. The teams consist of technicians with automation experience and technical experts to ensure close integration of business and technology.

What principles and methods are used in test automation?

Signal Iduna uses the Triple A principle (Arrange, Act, Assert) and the Rail Replacement Service (Setup, Execute, Verify). The business-driven test automation follows a behavior-based approach for complex projects. In addition, practice-oriented risk-based training is carried out, e.g. on equivalence partitioning and boundary value analysis.

What are the future prospects for business-driven test automation at Signal Iduna?

Further development focuses on agile working methods with a particular focus on the synthetic generation of test data. The aim is to disseminate successful experiences, promote continuous improvements and further increase the acceptance of automation in the company.