Insurance is a broad industry covering health, personal property, liability, automobiles, mortgages and more. With such a wide range, some companies specialize while others offer comprehensive product offerings. In the last year and a half, XBOSoft has worked together with another software company that mainly focuses on developing software for the insurance industry. During this time, we’ve accumulated knowledge in the insurance domain and have gathered some key points that we think are important for testing insurance software:
1. Roles & Permissions: These roles may include:

  • Insurance agent who submits the insurance application
  • Insurance company employee who mainly checks and approves (or declines) the application.
  • Administrator who has rights to set up the software.

These roles are totally different and have different permissions. It is critical to ensure that each role has correct rights. Defects in this part of the application may cause a big loss for the insurance company. Can you imagine that an insurance agent that can approve his/her own application?
2. Information interfaces: When testing insurance software, we need to verify that information not only can be saved in the front office but also can be saved and transferred through front, middle and back office (and vice versa) databases and operations without any errors.
3. Changes of numbers: Insurance is all about money and numbers. A trivial change of a number in a variable may cause a big difference in the final result. Usually, nearly every new release of the insurance software contains some changes in the numbers such as the interest or percentage of the provision fee. Therefore, data verification and checking all calculations is very important.

Some of the challenges for testing insurance software that we’ve met include:

  • Understanding domain knowledge: One application may include many insurance types. The requirements and workflow for these insurance types are also different. Even for the same type of insurance, there may be different workflows depending on the age or income of the applicant. Since, most software testers are not experts in insurance, understanding these complex rules presents a challenge. You have put yourself in the shoes of an insurance agent to understand all the rules and criteria.
  • Checking huge documents: This is not technically challenging but requires patience. Most insurance software applications contain large amounts of paper output and usually these documents have many pages. Information in the application must be checked periodically with paper output. Depending on the frequency that this task needs to be done, automated data verification testing can used to accomplish this task.

Insurance software testing is like any other domain specific related quality assurance work. You really need to understand business rules in developing thorough test cases and in prioritizing the test strategy. Otherwise, you can add very little value.