Vote UpVote

Why unit tests are not always good

The Programming Works – Unit tests are good to detect most bugs in your code but not all bugs. When you are writing standard unit tests for a class you are doing the following Create a fresh class instance (ex using Setup method in DUnit framework); Run a code under test (usually a single call of a single method) on the instance; Free the instance (ex using TearDown method in DUnit framework). And this is how unit tests should be written; if your test detects a bug you immediately know the bug’s origin. The problem with the above scenario is that it is ideal to hide some badly reproducible bugs such as access ...
Favorite? Off-Topic? Serg @ 2014-06-17 08:54


Visits: 831
Votes: 0
Favorites: 0
Off-Topic: 0

Visits by Source

User Actions

Users who voted for this posting

Contact us to advertise on DelphiFeeds.com

Community Links

Torry Firebird News


Please login or register to use this functionality.
(click on this box to dismiss)