Software Development Cross Solution - Index of - Free

Red, green, refactor...
Seriously? You made an empty class to get a test
to pass and you call that SUCCESS?
Test-driven development is about
doing the simplest thing you can to
get your test to pass.
Resist the urge to add anything you might need in the
future. If you need that something later, you’ll write
a test then and the code to pass that test. In the
meantime, leave it alone. Obviously you can’t stop
here—you need to move on to the next test—but
focusing on small bits of code is the heart and
soul of test-driven development.
Test-driven development works on a very simple cycle:
When you’re done refactoring,
move on to the next test and
go through the cycle again.
1
2
3
test-driven development
This is the YAGNI
principle... You Ain’t
Gonna Need It.
Red: Your test fails.
First you write a test that checks whatever functionality you’re about to
write. Obviously it fails, since you haven’t implemented the functionality
yet. This is the red stage, since your test GUI probably shows the test
in red (failing).
Green: Your test passes.
Next, implement the functionality to get that test to pass. That’s it. No
more. Nothing fancy. Write the simplest code you can to get your test
to pass. This is the green stage.
Refactor: Clean up any duplication, ugliness, old code, etc.
Finally, after your test passes, you can go back in and clean up some
things that you may have noticed while implementing your code. This
is the refactor stage. In the example for Starbuzz, you don’t have any
other code to refactor, so you can go right on to the next test.
Download at WoweBook.Com
you are here 4 281