2 added 2 characters in body; added 70 characters in body
source | link

Unit tests are for verifying that you have the correct algorithm and that you haven't had a regression on a fixed bug. The first should generally be testable in debug mode, the second might not -- if you'veyou have an error that only occurs in a particular build (optimized release for instance, or different level of optimization), then obviously you need to resrretest it in that releasebuild.

Unit tests are for verifying that you have the correct algorithm and that you haven't had a regression on a fixed bug. The first should generally be testable in debug mode, the second might not -- if you've error that only occurs in a particular release, then obviously you need to resr it in that release.

Unit tests are for verifying that you have the correct algorithm and that you haven't had a regression on a fixed bug. The first should generally be testable in debug mode, the second might not -- if you have an error that only occurs in a particular build (optimized release for instance, or different level of optimization), then obviously you need to retest it in that build.

1
source | link

Unit tests are for verifying that you have the correct algorithm and that you haven't had a regression on a fixed bug. The first should generally be testable in debug mode, the second might not -- if you've error that only occurs in a particular release, then obviously you need to resr it in that release.