Search type Search syntax
Tags [tag]
Exact "words here"
Author user:1234
user:me (yours)
Score score:3 (3+)
score:0 (none)
Answers answers:3 (3+)
answers:0 (none)
isaccepted:yes
hasaccepted:no
inquestion:1234
Views views:250
Sections title:apples
body:"apples oranges"
URL url:"*.example.com"
Favorites infavorites:mine
infavorites:1234
Status closed:yes
duplicate:no
migrated:no
wiki:no
Types is:question
is:answer
Exclude -[tag]
-apples
For more details on advanced search visit our help page
Results tagged with Search options user 22760

Unit testing is a method by which individual units of source code are tested to determine if they are fit for use.

14
votes
I do unittests, but not (or few) at work The main benefits of testing i get are, that refactoring is a whole lot easier and that regression (i.e., reintroduction of errors already fixed) is noticed. …
answered Jun 30 '11 by keppla
30
votes
The Granularity in your example seems to be the difference between unit- and acceptance tests. A unittest tests a single unit of functionality, with as few dependencies as possible. In your case, the …
answered Sep 23 '11 by keppla
4
votes
When strictly following the philosophy of unittesting (emphasis on unit), you should not create an Exe-file, but instead test if your class calls the interfaces to spawning and monitoring that process …
answered Aug 2 '12 by keppla
11
votes
What you describe may actually not be such a bad thing, but a pointer to deeper problems your tests discover As the system changes we find ourselves spending more time fixing broken tests. We have …
answered Sep 21 '11 by keppla