I’m currently working on an enhancement to an existing insurance premium rating algorithm. Anyone who has done work in insurance (whether it be in IT or on the business side) is probably well aware of how complex this can become.
Consequently, any significant enhancement to such a system is quite likely to be fraught with pitfalls and setbacks, and that’s even before considering the level and quality of business requirements and testing strategies. However, the existence of unit tests can help to minimize these risks.
Both unit tests that exist before development enhancements and unit tests you create as part of the development effort can be beneficial.
Existing unit tests benefit developers in at least two ways:
- They could be considered a form of requirements as to how the system currently operates. Unit tests provide concrete expressions of business requirements. For those who understand concepts better through examples (such as me), these existing tests can be invaluable. Even with well-written business requirements, sometimes understanding can only come through examples such as this. It also provides the developer with a debugging opportunity for deeper understanding of the existing code, should this be found to be necessary.
- They help to ensure that changes made by the enhancement do not break the existing system, or gives the developer a testing pathway, should the existing behavior need to be changed due to the enhancement.
New tests also provide their own benefits:
- It should be obvious that they help to ensure that code meets requirements.
- They also help to ensure that all logic conditions are accounted for. They force the developer to revisit the code they have just written and to approach it from different directions. This helps to root out conditions the developer might not otherwise think of, resulting in them to then alter the code to properly handle these conditions.
So, what are some ways we can ensure that we write unit tests with sufficient coverage? Below is a short list of some guidelines to follow:
- How many tests are enough? Nothing that can break should be left untested, even seemingly trivial ones.
- Most modern development environments have tools that will expose code that does not get executed during the run of your unit test suite. Use these tools to ensure you get the most thorough test coverage you can.
- Test boundary conditions, especially when testing something as complex as the algorithm I referred to in my introduction.
- Bugs tend to collect within the vicinity of each other. If one bug is found, it is good practice to thoroughly test the code around it, since it is likely other bugs will exist there as well.
- Lastly, and this can sometimes be difficult, tests must be as fast as you can possibly make them. When time gets short, it will be the longest running tests that get sacrificed first. As an example, I’ve had unit tests in the past that have processed over xml document provided as the result of a service call. These documents were huge, containing the data for entire policies, most of which we never even needed. To cut down on processing time, we edited these documents to contain only the data relevant to the tests being run.
Unfortunately, the decision to create unit tests or not isn’t always up to the developer. As I previously stated, I think most of those involved understand the importance on a theoretical level, but just are not willing to sacrifice the time up front to ensure that unit tests are written. However, as developers, we must try to incorporate them when we can.