Over time, I compiled a list of things regarding unit and unit integration tests; books, articles, forums and blogs. I have not always kept track of where I found some piece of information. So the references at the bottom of this article are not complete.
Recently I discovered the XUnit Test Patterns website by Gerad Meszaros (I wished I found that one earlier). Still I wanted to share with you the following list. This can maybe help to verify your effort in organizing and/or conducting unit (integration) tests. Maybe you have points to add? Or maybe you disagree? In any case, I would like to hear from you.
Unit testing is a process of testing the individual subprograms (classes), subroutines or procedures (methods) in a program. Most of the times, these “units” are tightly coupled with other modules. Sometimes the latter are stubbed out to assure that we only test the unit under test and not the secondary units. Unit integration testing concerns the inter-operation between the different units a developer has made. (Integration in the small.)
This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)
General News Suggestion Question Bug Answer Joke Rant Admin
Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.