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 14529

TDD stands for Test-Driven Development, or Test-Driven Design. It is the practice of writing a unit test before writing code to satisfy it, in what is known as the Red-Green-Refactor cycle.

0
votes
project will fail. Perhaps the requirements are complex and volatile, the infrastructure unstable, the team junior and with high turnover, or the architect is an idiot. On a TDD project, the symptom of …
answered Mar 6 '14 by soru
0
votes
Something like a date validation function would be a genuinely reusable component, and so should; have tests written against it's api already exist, probably as part of your language standard libra …
answered Sep 16 '14 by soru
0
votes
I would say this kind of thing is more suitable for RDD: Reading-Driven Development. This is where you read in a book the algorithm for something complicated like a Kalman filter, and then translate …
answered Mar 6 '14 by soru
1
vote
When faced with a philosophical quesion, drop back to the driving requirements. Is your goal to produce reasonably reliable software at a competitive cost? Or is it to produce software of the high …
answered Mar 27 '14 by soru
7
votes
One option is to use an in-memory testing database such as H2; it tends to be about about 10x faster than a standard disk-using database, and with lower startup/teardown times. Whether it will help …
answered Jun 30 '14 by soru
6
votes
My interpretation of that talk is: test components, not classes. test components through their interface ports. It's not stated in the talk, but I think the assumed context for the advice is somet …
answered Mar 30 '14 by soru
0
votes
The core idea of TDD is that, by writing tests first, you end up with a system that is, at the least, easy to test. Hopefully it works, is maintainable, well documented and so on, but if not, well at … least it's still easy to test. So, if you TDD and end up with a system that is hard to test, something has gone wrong. Perhaps some things that are private should be public, because you need them to …
answered May 20 '14 by soru
11
votes
philosophically, tests that use mocks should take priority over tests that use a live endpoint I think at the very least, that's a point of current ongoing controversy amongst TDD proponents …
answered Mar 18 '14 by soru
6
votes
Fix random seed. For 1, 2, 5 and 12-sided dice, confirm that a few thousand rolls gives results including 1 and N, and not including 0 or N + 1. If by seem freak chance you get a set of random results …
answered Mar 5 '14 by soru
0
votes
TDD shouldn't be used when some alternative approach is more appropriate. The key thing to remember is that the alternative approaches aren't so much manual testing, as things like: Write and … testing being especially difficult for some reason is one factor that might guide the choice of design method. But it is far from the key factor; in fact several of the other approaches will end up doing as much, or more, automated testing than TDD. …
answered Apr 4 '14 by soru