Just Unit Testing

摘要

This paper came about for the simple reason that we had to test some new software we had not developed. This software (the Intel Transport Interface) was a library with a public API, and was to be part of a kit included with pre-production systems. Digging into the system, we found that the developer did not have any unit tests, so we wrote some as part of our test plan. We decided to use an Open Source framework and Mock Objects. Along the way, we found some interesting problems using the most popular C++ Unit Test framework (CppUnit), and that organizational problems can be a more significant issue than we had realized. Ever-changing market trends, a vast selection of business technologies, and process theory inundation all create environments that must be adapted to quickly and impacted the decisions we made. For instance, we have learned to downplay much of the latest process terminology, not necessarily thinking about "Extreme" or "Agile", even though that is what we eventually end up doing. We have not convinced the ITI developer to use unit tests, and doubt we ever will before the project eventually reaches end of life, but the lessons we have learned from this experience are influencing our future development plans.