Editing
Test-Driven Development
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== <span style="color: #FFFFFF;">Evaluating</span> == Evaluating TDD: # '''Speed''': Does TDD take "Too long"? (While it takes longer to write the first line of code, it saves weeks of "Debugging" and "Maintenance" later). # '''Legacy Code''': How do you use TDD on an old app with 1 million lines of code and zero tests? (The "Testing Hole" problem). # '''UI Testing''': Is it possible to use TDD for "Art" or "UI Design" where there is no "Right Answer"? # '''Motivation''': Why is it so hard for developers to stay in the TDD "Habit"? (It requires intense discipline to write the test first when you are in a rush). </div> <div style="background-color: #2F4F4F; color: #FFFFFF; padding: 20px; border-radius: 8px; margin-bottom: 15px;">
Summary:
Please note that all contributions to BloomWiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
BloomWiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Search
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information