posts - 4236, comments - 3946, trackbacks - 366

My Links

News



Subscribe Subscribe

image image image





This is my personal weblog. These postings are provided 'AS IS' with no warranties, and confer no rights. The views expressed on this weblog are mine alone and do not necessarily reflect the views of my employer.

Licenza Creative Commons

Tag Cloud

Archives

Post Categories

Quando fare i check-in se si usa il Test Driver Development...

Un articolo molto interessante di Peter Provost che alla fine mostra questi passi:

    1. Write the test code.
    2. Compile the test code. (It should fail because you haven’t implemented anything yet.)
    3. Implement just enough to compile.
    4. Run the test and see it fail.
    5. Implement just enough to make the test pass.
    6. Run the test and see it pass.
    7. Refactor for clarity and to eliminate duplication.
    8. Pull updates from the server to get any changes from other people
    9. Compile the code, fix it if it is broken
    10. Re-run all tests, to see if others' changes have broken your tests. If they pass go to step 11 if they fail go to step 5.
    11. Check in the code
    12. Repeat from the top

Il resto lo trovate qui.

Print | posted on Saturday, April 9, 2005 12:53 AM |

Comments have been closed on this topic.

Powered by:
Powered By Subtext Powered By ASP.NET