Feature/Function Testing: What is it and why is it important? by Jim Jenkins

I. WHAT IS FEATURE/FUNCTION TESTING?

Voice business solutions involve menu-driven processes that allow customers to perform a wide range of self-service activities. A key requirement for successfully implementing and maintaining these business solutions is the ability to test them before and after they have been deployed, in order to confirm they work as designed. To thoroughly test the solution, every path a customer can take, including those associated with entry errors, must be tested. Within the industry, this kind of testing is referred to by many different names including, “unit level testing,” “feature testing,” “function testing,” “regression testing,” “flow testing” or “dialog traversal testing.” The purpose of this paper is to discuss this testing requirement as it relates to voice business solutions. IQ Services refers to this type of testing as “Feature/Function Testing.”

II. WHY IS FEATURE/FUNCTION TESTING IMPORTANT?

The return on investment (ROI) for self-service business solutions is dependent upon having well-designed applications that work both when they are introduced and later on, in production. Feature/Function Testing during development verifies the application has been programmed correctly and reduces the schedule risk created by this critical activity. Feature/Function Testing, as a key part of customer/user acceptance testing, ensures a business solution is ready for use by customers. Feature/Function Regression Testing after deployment ensures that periodic changes to the business solution infrastructure or to the solution content does not affect the quality of the customer experience. In today’s environment where customer satisfaction is a key element of customer loyalty, a business solution that delivers a good end user experience is critical to meeting business objectives.

III. WHEN AND HOW SHOULD FEATURE/FUNCTION TESTING BE PERFORMED?

Feature/Function Testing is a task that is frequently on the critical path of business solution implementation. It may be performed by the developer of the business solution or in some cases the end user who is purchasing the solution from a vendor. In either case it is important to perform the testing as soon as the configuration and/or programming of the application is completed and a test bed is available. Regardless of who performs the test, it must be done in a disciplined, well-documented manner that quickly identifies errors and verifies fixes. Testing during the development phase is not about acceptance; it is about management of the development process. After testing is complete and the solution performs as designed, there may be a period of time when other work must be completed before the solution is deployed. It is good practice to perform the Feature/Function Testing again as part of the final user acceptance testing, which typically also includes performance/load testing. If the testing is set up correctly during the development phase the acceptance test phase becomes a regression test that can be performed very effectively in terms of both time and cost.

Business solutions frequently change early in life when customers provide feedback on how solutions can be improved and when more options become available. It is important to periodically perform Feature/Function Testing to ensure not only that new features work as designed but also to confirm that changes to the solution have not negatively affected business solution performance. If the Feature/Function Testing has been properly setup during the project implementation phase, additional post-implementation testing can be done in a timely and cost effective way.

IV. IMPORTANT ISSUES AND CONSIDERATIONS RELATED TO FEATURE/FUNCTION TESTING

During Planning:
• Quality application documentation increases the effectiveness of testing
• When designing a business solution, you should take testability into consideration
• Remember to include an extra iteration of testing in your planning to mitigate cost and schedule risk
• You should provide a dedicated test system during the development phase of a project, if possible
• Good test discipline and documentation are key to quick problem resolution and regression testing
• It is important to use someone other than the business solution developer to perform Feature/Function Testing

For Business:
• Well-planned, implemented and documented Feature/Function Testing will add value through the entire business solution life cycle
• Thorough, disciplined and repeatable Feature/Function Testing will reduce risk during implementation and on-going risk related to customer satisfaction
• Feature/Function Testing during the development phase may not be adequate for user acceptance

In General:
• Recording of test calls significantly enhances testing process and problem resolution
• An automated process increases test effectiveness and makes regression testing practical

CONCLUSION

Feature/Function Testing is not an option in implementing and maintaining today’s complex business solutions; it is a necessity. Business solutions must be well designed and must work well for customers to ensure a good end user experience. Good quality assurance practice dictates that disciplined, effective testing to demonstrate and document performance should be done at the appropriate times during a business solution life cycle.

Back