She voted against the broadening of eminent domain! That is enough for me to respect her more than any of the other judges who voted for taking peoples property away.
Sure! Granted the code is modular and can be tested independently. Just make sure that your input is as thin of a layer as possible. For example all the code that deals with actually calling the system to get processes should be a couple of lines long (ie, bullet proof since you can't really test that). Than you create a mock version of that function that returns some predefined data. In your tests make sure that your formatting functions and any calculation functions use this mock function and do those tests that way. For the actual gui, I believe you can do screen dumps. Although you can't test the dynamic nature of the gui being updated, you can at least capture one slice of the gui displaying so that if you ever refactor the display code it will at least produce an identical looking screen.
Remember, the best unit test writers are the laziest ones. This is very important because if you write more tests than you need (out of being a perfectionist for example) you'll end up with a lot of code that will need to be changed if the requirements change.
Refactoring unit tests is very dangerous, but sometimes it's better to refactor your tests so that you have the desire to continue writing them. Than to end up with some crappy tests that you hate so much that you just stop writing new ones or even delete the old ones because requirements changed and you don't feel like updating them.
Unit testing my code has saved me hundreds of hours of debugging time, unit tests are also great documentation. In a big system where you can't keep track of all the code and how it works in your head, unit tests act as little documentation beacons showing how some piece of code works.
Slashdot Mirror
How can you respect someone if you blatantly see them destroying this nation? Boggles the mind...
She voted against the broadening of eminent domain! That is enough for me to respect her more than any of the other judges who voted for taking peoples property away.
I'm totally with you on that one!
Try google!
;-)
Search for "php unit testing"
If you're too lazy, here are some links:
Unit Testing in PHP
PHPUnit
Happy unit testing!
Sure! Granted the code is modular and can be tested independently. Just make sure that your input is as thin of a layer as possible. For example all the code that deals with actually calling the system to get processes should be a couple of lines long (ie, bullet proof since you can't really test that). Than you create a mock version of that function that returns some predefined data. In your tests make sure that your formatting functions and any calculation functions use this mock function and do those tests that way. For the actual gui, I believe you can do screen dumps. Although you can't test the dynamic nature of the gui being updated, you can at least capture one slice of the gui displaying so that if you ever refactor the display code it will at least produce an identical looking screen.
Remember, the best unit test writers are the laziest ones. This is very important because if you write more tests than you need (out of being a perfectionist for example) you'll end up with a lot of code that will need to be changed if the requirements change.
Refactoring unit tests is very dangerous, but sometimes it's better to refactor your tests so that you have the desire to continue writing them. Than to end up with some crappy tests that you hate so much that you just stop writing new ones or even delete the old ones because requirements changed and you don't feel like updating them.
Unit testing my code has saved me hundreds of hours of debugging time, unit tests are also great documentation. In a big system where you can't keep track of all the code and how it works in your head, unit tests act as little documentation beacons showing how some piece of code works.
Twisted is a networking framework in Python which has a lot of unit tests:
http://www.twistedmatrix.com
Take a look at Zope3 it has some 5,000 unit tests:
http://cvs.zope.org/Zope3/
Take a look at some of the reasoning for this Kite idea:m
http://www.fdsmail.com/archeologee/Discoveries.ht